Own genesis
Independent Daisybee regtest genesis, ports, chain ID and address namespace.
A tiny Bitcoin-family experiment. No sale. No public mainnet yet. Built slowly, in public when it is ready.
Daisybee is still a development network. The point right now is to make the code less inherited, more understandable, and increasingly boring to run.
Independent Daisybee regtest genesis, ports, chain ID and address namespace.
daisybeed and daisybee-cli build and pass the local smoke check.
Inherited Namecoin interfaces are being disabled and removed in controlled steps.
No public mainnet until the merged-mining/security arrangement is credible.
The current public-facing story is the development history, not a price chart.
Daisybee binaries, independent regtest network parameters and genesis.
Own runtime paths plus the first packaged Linux developer snapshot.
Name transactions rejected; inherited name RPC surface removed from normal use.
Inherited NameHash index physically removed from the runtime/build path.
These are constraints, not marketing copy. If Daisybee ever becomes more public, they stay visible.
The first income route is deliberately ordinary: small Daisybee products paid in pounds through Stripe. No coins, yield, mining advantage or investment benefit comes with a purchase.
We already have an active Stripe account, so v1 uses Stripe Payment Links rather than building a checkout system. The first product is now live through Stripe. Other physical products remain previews until fulfilment is ready.
Wallpapers, transparent icons and a printable art card · £3
Small physical pack · target £4–£5
Simple art print · target £8–£12
Digital pack + stickers + print
We are not deleting the idea of voluntary support, but it is no longer a three-tier pseudo-membership. When enabled, it should be a single optional Stripe pay-what-you-want route with explicit wording that it buys no coin, return, governance right, access right or future entitlement.
No. There is no public sale, ICO or public mainnet. The project is currently software under development.
No. It is a separate Bitcoin-family experiment with Bitcoin/Namecoin technical heritage and its own network identity.
A tiny standalone SHA-256 chain is easy to overpower. The intended mainnet security model is merged mining, but code support is not the same as actual miner participation.
Only the listed ordinary product or artwork. They do not buy Daisybee coins, investment rights, governance, yield, mining advantage, preferential access or any future entitlement.
Because the project has no reason to pretend urgency. Breaking a private testnet is cheaper than discovering a bad assumption after a public launch.
No. Mainnet remains conditional on credible security. The software and artwork can remain useful even if that gate never opens.