What decentralised really means

The original idea

The Bitcoin whitepaper is titled "Bitcoin: A Peer-to-Peer Electronic Cash System." Its first sentence describes payments "sent directly from one party to another without going through a financial institution."

The introduction names the problem. Online commerce relies "almost exclusively on financial institutions serving as trusted third parties."

And it names the goal: "an electronic payment system based on cryptographic proof instead of trust."

That is the starting point. No middleman you have to trust. Rules you can check yourself.

Where crypto drifted

Then the middlemen came back.

Many people do not hold their own coins. An exchange holds them for them. That is convenient. It is also exactly the trusted third party the whitepaper wanted to remove.

The record is long.

Mt. Gox lost about 750,000 customer bitcoin in 2014.

FTX collapsed in November 2022. Customer deposits had been funnelled to a sister trading firm. At sentencing in March 2024, the judge found that customers had lost $8 billion.

On 21 February 2025, about $1.5 billion was stolen from Bybit. The FBI attributed it to North Korea. The attackers did not steal the keys. They compromised the signing software. The screen showed the signers one transaction. They signed a different one.

On 24 September 2026, Bitget was hit. Hot and warm wallets were drained. The first reported loss was $351.6 million, later revised to about $387 million. North Korea is suspected, not confirmed. Fortune reported that the attackers "tricked Bitget's internal approval system into authorizing the transfers."

Different years. Same shape. One place holds everyone's money. When that place fails, everyone loses.

To be fair: Bitget says it covered the loss from its own protection fund. When a decentralised contract fails, there is often nobody to pay. That is the trade-off.

The quieter drift: DAOs with a hand on the wheel

Custody is the visible drift. Governance is the quiet one.

Many projects have a DAO. Holders vote. It looks decentralised. Look closer, and you often find one of two things.

One wallet decides. In June 2022, Solend held a vote to take over a large borrower's account. According to The Block, 88 % of the voting power for it came from a single address. A second vote reversed it the next day.

Someone acts first and asks later. In April 2023, the Arbitrum Foundation asked its DAO to approve 750 million ARB. According to The Block, the tokens had already been moved, and some had already been sold. Holders voted heavily against. The Foundation split the proposal and promised transparency reports. Holders pushed back, and it worked.

A Tezos co-founder called this "decentralization theater." A January 2025 report by the EU regulators EBA and ESMA describes similar patterns: governance tokens "can be concentrated in a very small number of holders."

The test: custodian yes, override no

So where does decentralisation start?

Not at the question "is there a company somewhere?" Somebody always holds operational keys. Somebody pays for servers. Somebody signs with a hosting provider. That is custody of infrastructure. It is not holding anyone's tokens. And it can be shared, audited and replaced.

Our whitepaper puts it in four words: Custodian, yes. Override, no.

Here, custodian means holding keys and access. It does not mean holding holders' funds. A group that holds keys removes a single point of failure. A group that can change how funds are distributed, or overrule a vote, is the problem it was meant to solve.

The difference is between who holds the keys and who may change the rules.

That gives three questions for any project:

1. Who can change the rules? Fees, supply, voting settings, upgrades.
2. Who can override? Pause, veto, move funds without a vote.
3. Where is the single point of failure? One key, one signer, one server, one person.

If the answer to the second question is "a board" or "the founder", the DAO is decoration. A label does not change who holds the levers.

Where it ends

Some parts stay central even in the best case. The website. The node you read from. The company that sells you your first token. The social accounts.

A project cannot remove them. It can make them replaceable, so no single one can hold the rest hostage.

And when nobody can override, what remains is the code. Decentralised systems lose money too. On 1 April 2026, Drift, a decentralised exchange on Solana, lost about $285 million after a new market allowed borrowing against an illiquid token. Here the weak point was design and parameters, not custody.

Remove the man in the middle, and contract security is what is left.

Regulation in plain words

This is a description, not legal advice. We make no claim about how any rule applies to Shiba Classic.

The EU's crypto rulebook is MiCA. Its stablecoin rules have applied since 30 June 2024. The rest has applied since 30 December 2024.

MiCA has rules for those who offer tokens to the public or seek their admission to trading. For services, it draws its line at intermediaries. Custody for clients, trading platforms, exchange services and order execution need authorisation as a crypto-asset service provider (CASP). Already-regulated firms such as banks can also qualify.

The transition period ended EU-wide on 1 July 2026. Germany ended it earlier, on 31 December 2025. In June 2026, ESMA said unauthorised providers must stop onboarding new EU clients. Their clients "do not benefit from MiCA safeguards."

What about decentralised systems? Recital 22 says the rules still apply where part of a service is decentralised but someone provides or controls it. It then says services provided "in a fully decentralised manner without any intermediary" should fall outside the regulation. A recital guides interpretation. It is not an operative rule.

MiCA does not define "fully decentralised". EBA and ESMA say so directly. A Commission answer in ESMA's Q&A register says it is "assessed on a case-by-case basis by the competent authorities."

What might count? The Commission's 2026 MiCA review consultation asked for views on candidate criteria. They are not law. Among them: an identifiable intermediary, admin keys over key functions, concentrated governance power, custody of user assets.

Our three questions are a way to think about control. They are not the legal test. Authorities decide each case on its own facts.

A common claim is that tokens whose projects offer staking face higher listing hurdles. The rules we found concern the provider, not the token. MiCA has no rules written for staking. When an intermediary offers staking to clients, it is treated as part of custody, and the obligations sit with that intermediary.

One more point matters for listings. Since July 2026, an exchange serving EU clients needs authorisation, and it must assess every token it admits.

Do we still need centralised exchanges?

A centralised listing brings real things. Visibility. Easy fiat access for newcomers. An order book.

It also brings costs. Industry reporting by crypto.news puts listing fees at the largest venues between $100,000 and $3 million, plus market-maker retainers and escrow deposits. And tokens sit in someone else's custody again.

Meanwhile the landscape moved. In January 2021, decentralised exchange spot volume was 6 % of centralised volume, according to CoinGecko. In November 2025 it was about 21 %. Most trading still happens on centralised venues. But the gap has narrowed a lot.

Self-custody wallets now have buy buttons. Card, bank transfer, mobile pay, without leaving the wallet. Many route swaps across several decentralised exchanges at once. The fiat entry point is still a regulated company. The middleman shrank. It did not vanish.

The counter-case is real. A thin pool gives large trades a worse rate. An order book with a market maker can absorb that. And self-custody has its own failures: lost seed phrases, phishing, drainer approvals, fake tokens with our name. A decentralised exchange removes the custodian. It does not remove the risk.

The maintainer's view is no. But in a decentralised project that is not his call to make. It belongs to holders.

Where Shiba Classic stands

We hold ourselves to the same three questions.

Who can change the token? Nobody. Ownership of the SHIBC contract was renounced on 13 November 2024, and we checked it before the community took over. On 4 October 2026 it is still renounced. It cannot change back. Nobody can raise fees, stop trading or mint. The token contract was audited by Hashlock and rated Secure.

Who can pull the liquidity? Nobody. The pool's LP tokens sit at the dead address.

Who got tokens for free? Nobody. There was no allocation, no team wallet and no fundraise. Everyone, the maintainer included, bought on the open market. About 40 % of the supply is burned.

Who can change the DAO's rules? Only the DAO. It runs on Aragon, and the maintainer holds no admin key over it.

The full record, with every address and every check, is in our whitepaper.

Why one person drives today, and where it goes

Today the maintainer drives most decisions. That is a phase, not the goal. A community takeover needs someone to put the project on the right track: rebuild, ship, and set up the structures that make him replaceable. He does not decide in a vacuum. Ideas go to people from the community first, and their view counts.

The end state is a project that belongs to nobody. No owner, no maintainer with special rights.

People still do the work. But they work for the DAO, not the other way round. Developers, operators and the maintainer himself become contract partners. Each has a framework contract with a clear scope. They are paid from the treasury or the operations wallet. Every month the contract is checked: is the work still needed, is it still being delivered? Then it renews, or it ends.

Open the diagram in full size

This is not a new idea. The ENS DAO runs a service provider program. Providers apply with a yearly budget, holders vote on who is funded, and the DAO can stop a stream at any time.

The handover has a written rule (whitepaper §6.7). The bootstrap phase ends after Q1 2027, once a proposal has passed with at least 10 addresses other than the maintainer's, together holding at least 5 % of the total supply. Both are published commitments, not contract rules. Hold us to them.

The steps on the way are set: emergency access, a second key holder, a multisig as custodian, then a team from the community. For decisions we plan conviction voting, where support builds over time and rule changes need a waiting period.

One honest limit of the voting contract itself. Aragon's token voting weighs every wallet by its full balance and measures participation against the wrapped supply, not against all SHIBC. A rule that counts addresses can be gamed by splitting one holding across many wallets. How the DAO should guard against concentration is an open question. It belongs to holders.

SHIBC is meant to be used in products. We promise no yield, no payouts and no price outcome.

How voting works

Voting power is not handed out. A holder deposits SHIBC into the wrapper contract and receives gSHIBC one to one. Withdrawing burns the gSHIBC and returns the same amount of SHIBC, at any time, with no lock and no fee. The vote is active from the first deposit, no extra step. gSHIBC only counts votes. It carries no payout and no return. The wrapper is Aragon's standard contract, not our own code.

Opening a proposal takes 200 billion gSHIBC, 0.02 % of supply.

A DAO with no voters is not decentralised either. It just leaves the decision with whoever is still there.

So here is a question for those who already hold SHIBC: should a decentralised project chase centralised listings at all?

That is not ours to answer alone. That is the point.