Joined May 2026
- Tweets 48
- Following 41
- Followers 151
- Likes 21
4 Photos and videos
Pinned Tweet
Jun 3
Adamant update : it's been a minute.
Quick recap of where we are:
The L1 is deep in build. Privacy-default by design, post-quantum sigs, built to handle real volume. Bytecode verifier shipped. Runtime is ~93% complete. Phase 6 (privacy layer) is next, then mainnet.
But the protocol on its own isn't the point. The point is what people actually use.
So here's what Adamant is becoming:
Chain → privacy-default settlement layer
Bridges → bring assets from BTC, ETH, stablecoins onto Adamant
Device → hardware-secured phone-form-factor purpose-built for sending, spending, saving crypto without the friction
Ledger but usable. Saga but built around a chain designed for it. Cash-like UX backed by hardware-grade security.
Crypto today is two worlds — the technical underground and the apps that copy banks. Neither is what people actually want. The real merge of crypto and everyday life needs both the rails and the device.
That's what we're building. Years of work ahead. Heads down.
More soon.
2
1
9
197
Jun 3
Adamant has two halves.
The chain decentralised, privacy-default, post-quantum. No investors, no central control. That's not a marketing line; it's the design. Infrastructure that belongs to no one.
The hardware software a purpose-built device for crypto. Self-custody by default. Multi-chain by design. Adamant-settled. Bridged to BTC, ETH, stablecoins.
Two halves, one mission: bring crypto out of the technical underground and into something people actually use.
The chain doesn't take investment. The product side does that's where execution lives.
Open for conversations.
1
2
6
149
May 16
We are still building behind the scenes for the people asking been a lot going on, some exciting developments are happening!
6
2
12
282
May 12
Adamant update.
The site. Adamant Protocol is rebuilt as a working hub.
Five doors route from the home page: use ADM, run a node, build on it, audit it, understand it.
/start is the protocol in five steps with diagrams.
/network is a full block-explorer scaffold search, blocks, per-transaction pages with the public-view vs view-key-disclosure split, validator detail with cohort markers, the two-regime mempool inspector (threshold encryption at N≥15, time-lock VDF below), burn-to-mint registry, Genesis NFT registry.
/developers has the JSON-RPC reference, the Adamant Move walkthrough, run-a-node with config.toml, view-key encoding, ML-KEM-768 stealth-address derivation, per-source-chain burn-tx format.
/security publishes audit progress per primitive, the signing-key roster with Ed25519 ML-DSA fingerprints, reproducible-build SHA-256s.
/tokenomics has the validator-APR calculator, the slashing-condition catalog, the multi-dimensional fee market.
/roadmap lists five stages with entry conditions, not calendar dates.
The protocol. The reference implementation is public, Rust, Apache 2.0: <github.com/adamant-protocol/…>. Ten crates.
Phases 1–5 complete: foundation, cryptographic primitives, transactions and lifecycle, AVM verifier with the cross-module rule walker.
Phase 5/6 AVM Runtime is ~93% (bytecode dispatch, multi-dimensional gas accounting, transaction-boundary integration).
Phase 7 consensus and networking foundations is now active.
Today's track:
· Binary quadratic form arithmetic
· Class-group composition and fast squaring (Cohen 5.4.7 / 5.4.8)
· Hash-to-class-group element via Tonelli–Shanks
· Wesolowski VDF — evaluate, prove, verify
· Time-lock envelope encryption (§3.8.8)
· Threshold-mempool regime hysteresis (§3.6, §8.4)
· ML-DSA-87 added as opt-in post-quantum signature variant alongside ML-DSA-65
Whitepaper amended in lockstep — §3.8.6, §3.8.7, §3.8.8, §6.2.1.9, §7.0, §7.2.2 Pallas, §7.3 value-commitments all landed today.
Pre-launch. Specification phase. The chain self-activates the moment seven Node Runners are simultaneously registered, stake-eligible, and online.
The whitepaper is the source of truth. The code implements it. The site reads from both.
1
1
12
648
May 11
How does the first DEX on Adamant actually get liquidity when everything starts with burn-to-mint?
Here’s the exact economic bootstrap from the whitepaper (no team pre-seed, no foundation wallet):
1. Burn-to-mint is the only initial supply path (70% of the fixed 100M ADM genesis pool).
Anyone burns BTC, ETH, USDT or USDC on their original chain → Adamant’s on-chain light client verifies it → protocol instantly mints ADM to your address at fixed public rates.
2. Economics in action:
• Early burners now hold real ADM (they paid market value in BTC/ETH/stablecoins).
• They use part of it to stake the minimum (1,000 ADM) and become validators.
• Once 7 validators are live → the chain self-activates automatically. No coordination, no insiders.
The other 30% of the genesis pool is released gradually as validator block rewards — so more ADM flows out naturally over time.
3. DEX liquidity forms organically:
Early ADM holders (burners validators earning rewards) can now provide liquidity to a community-deployed native DEX (Adamant Move smart contract).
They pair their ADM with bridged USDC/ETH/etc.
Result: Real economic skin-in-the-game liquidity from day one.
More burns → more circulating ADM → deeper pools → more trading → more confidence.
Pure market-driven bootstrap.
Full details (Section 10.2 8.1).
4
10
278
May 11
Adamant whitepaper key design choices:
• Credible neutrality (no foundation/premine/admin keys) privacy by default 50k TPS on residential fiber phone-verifiable history via recursive Halo 2
• Dual-regime encrypted mempool (threshold encryption time-lock VDF bootstrap)
• Hybrid post-quantum crypto (ML-DSA signatures ML-KEM stealth addresses)
• Permissionless prover market validator fallback for guaranteed proofs
• Protocol-enforced mutability declarations on every object/contract
• Dynamic FCFS validator set with transferable slots multi-tier participation
• Genesis pool: 70% public burn-to-mint 30% validator rewards
• Adamant Move bytecode with mandatory privacy/mutability metadata native verifier
1
9
236
May 11
Every account on Adamant is a smart account from day one.
No EOA vs contract split.
Full account abstraction native.
Adamant Move brings:
• Linear types & resource safety (no accidental fund loss)
• Object-centric model with explicit mutability
• Privacy by default via shielded functions
This is next-gen smart contracts. 👇 #AdamantProtocol
2
9
162
May 10
Four ways to participate in Adamant Protocol, Two staked roles secure the chain. Two permissionless markets serve it.
Anyone can join either market without permission and without stake you can take a staked role by simply meeting the floor.
Node Runner → Consensus participant (STAKED)
Node Watcher → Attestation, DA sampling, fraud detection (STAKED)
Prover → Recursive proof generation (PERMISSIONLESS)
Service Node → Light-client infrastructure (PERMISSIONLESS)
Hardware requirements, compensation details, and set sizes in the graphic
Full specs & whitepapers here:
→ github.com/adamant-protocol/…
→ adamantprotocol.com/about
Which role are you picking? Drop it below
#AdamantProtocol #Blockchain
7
12
301
May 9
Where the burn goes.
Getting this question a lot, so worth answering plainly.
1. The external value you burn (BTC, ETH, USDT, USDC) goes nowhere.
You burn it to a verifiably unspendable address on its source chain the Bitcoin null address, Ethereum's 0x000...dead, the equivalent on Tron and Ethereum for stablecoins.
The chain sees the cryptographic proof of burn and mints ADM to your Adamant address. Your burned crypto is permanently destroyed. No foundation receives it. No developer wallet receives it. No treasury holds it. It is gone, mathematically, forever.
There is no party on the receiving end of the burn. That's the entire point — it's how the chain bootstraps without a foundation collecting funds.
2. The ADM you receive is minted from the genesis pool.
A fixed pool of 100,000,000 ADM exists at protocol launch, partitioned 70M for burns and 30M for validator block rewards. When you burn, ADM is minted to you from the burn-allocated 70M sub-counter at the rate of 20 ADM per USD-equivalent burned. The pool drains as people burn and as validators earn. No new ADM appears outside this mechanism during the launch phase.
3. ADM you stake stays yours.
Staking doesn't transfer ADM anywhere. It locks ADM in your address as a behaviour bond slashable for misbehaviour, otherwise still owned by you, returned (subject to the 28-day unbonding window) when you exit. No staking pool, no validator escrow contract holding your funds, no third party ever takes custody.
4. What happens if the pool isn't fully claimed.
The launch phase ends when the pool is fully drained or, at latest, five years from genesis whichever comes first. If the five-year cap is reached with ADM still unclaimed in either sub-counter, the unclaimed ADM is destroyed. Not redistributed. Not held in reserve. Not allocated to validators or to anyone else. The unclaimed portion of the pool simply ceases to exist.
This preserves the no-insider-allocation property. No party gains from low launch-phase participation. The chain's circulating supply at the end of the launch phase is exactly what was claimed during it nothing more.
After the launch phase, the protocol's perpetual issuance schedule takes over (4% of supply Y1-5, 3% Y6-10, 2% Y11-20, 1% perpetual thereafter), paying validators continuously while transaction fees burn supply back. The expected long-term equilibrium is rough supply stability with mild deflationary pressure under sustained usage.
Spec: §10.2 of the whitepaper at github.com/adamant-protocol covers all of this in detail.
adamantprotocol.com/genesis
9
2
26
848
May 9
why am i building this, the problem isnt one bank or one government. its that whoever is in charge can change the rules whenever they want. banks freeze you. foundations dilute you. platforms ban you. every system that touches money eventually builds a way for someone with power to do something to someone without it, bitcoin fixed money. nobody can change bitcoin. but you cant build on it, ethereum let you build. but the foundation has changed the rules five times since 2015.
you shouldnt have to pick
so i made adamant. a chain you can build on where the rules cant be changed by anyone. including me. no foundation no premine no admin keys.
7 validators come online and it runs. after that i have no more power over it than you do. thats the point.
1
8
169
May 8
Adamant bytecode-verifier: feature-complete and production-side Sui-free as of today.
Originally forked from Sui-Move's move-bytecode-verifier. Phase 5/5b.5 tore out the Sui dependency entirely — petgraph and adamant-native crates only in the production graph. Build-system check enforces it.
1,585 tests. Eleven validation rules covering privacy consistency (single-module cross-module), type safety, reference safety, no dynamic dispatch, no native functions, bounded loops, no global storage. Cross-module privacy enforcement via ModuleResolver trait ready for the AVM runtime to consume.
Apache 2.0.
github.com/adamant-protocol
1
7
200
May 8
Adamant: validator slots, genesis cohort, and the launch incentive.
Today's whitepaper update specifies two new mechanisms that change how the chain bootstraps.
Validator slots are transferable.
The active set has 75 slots at launch. Once you hold one, you keep it as long as you stay online but you can also transfer it to another address by mutual consent. Sell it, gift it, pass it to family. The chain doesn't set a price, doesn't take a fee, doesn't restrict who you transfer to. You and the buyer agree off-chain or via on-chain auction; the protocol handles the atomic handoff.
This is a deliberate design choice. Over time, slots will concentrate with whoever can offer the most for them. The chain accepts that trade-off in exchange for a strong launch incentive: the first 75 validators capture the upside of having bootstrapped a network that didn't exist before they showed up.
The genesis cohort.
The first 75 validators to take active-set slots are the genesis cohort. Two artefacts mark them:
A permanent on-chain marker attached to their address. Records position (1 through 75), activation epoch, and chain-state commitment at the moment of activation. Non-transferable. Stays with the original address forever, even if the slot is later sold. This is the chain's record of who was there.
A Genesis NFT, freely tradeable, minted at activation. No protocol function. Pure cultural artefact. Bitcoin equivalent: imagine if Satoshi-era miners had received numbered "I was at genesis" NFTs. Those would be worth millions today.
Once 75 distinct addresses have taken slots, the cohort closes. Slot 76 onward is a regular validator slot, with no marker and no NFT.
What this means in practice.
If you're one of the first 75 to register, validate honestly, and stay online, you walk away with: years of validator earnings, appreciated ADM, a tradeable Genesis NFT, a permanent on-chain marker recording your role in bootstrapping the chain, and the option to sell your slot at any time for whatever the market pays.
The chain self-activates the moment 7 of these 75 are simultaneously online. There is no application process, no foundation approval, no recruited cohort. First seven to burn external value, register, and stay online bring the chain to life.
Spec: github.com/adamant-protocol
5
13
348
May 8
Adamant Protocol Development Status
The v0.1 specification is complete. After an extensive design phase incorporating five integrated proposals low-coordination launch, two-regime mempool encryption, permissionless prover market, hybrid post-quantum signatures, and the four-tier participation model every protocol parameter is now concrete. No placeholders remain.
Specified and finalised: Cryptographic foundation: Ed25519 ML-DSA hybrid signatures, ML-KEM-768 post-quantum key agreement, Halo 2 zero-knowledge proofs, Wesolowski VDF time-lock encryption, BLS12-381 aggregation.
Consensus: DAG-BFT (Mysticeti-shaped), constitutional floor of 7 validators, soft ceiling of 75, first-come-first-served selection with persistent membership.
Economics: 100M ADM genesis pool, 70/30 burn-to-validator split, 20 ADM per USD-equivalent burn rate, 1,000 ADM Node Runner stake floor, 100 ADM Node Watcher stake floor, scheduled five-year parameter re-evaluation.
Throughput floor: 50,000 TPS at design-target validator count on residential-fibre hardware.
Remaining work, in sequence:
Reference implementation in Rust. Pre-Phase-1 currently the protocol is fully specified but no production code exists. Estimated 18–36 months across cryptographic primitives, object model, privacy layer, consensus, recursive proofs, and genesis tooling.
Empirical validation of the 50,000 TPS floor on representative residential-fibre topology. The figure is provisional until measured. If empirics fall short, the floor is revised not the hardware tier raised.
External audits of cryptographic implementations, consensus correctness, and economic mechanisms.
Public testnet with stepwise feature activation, followed by an extended stability period.
Genesis activation autonomous, occurring the moment seven independent validators are simultaneously registered, stake-eligible, and online.
No coordination event. No recruited cohort. No foundation.
Repository: github.com/adamant-protocol
14
280