BDAG BURN · PUBLIC EVIDENCE

A public burn vault
for native BDAG.

Any participant may voluntarily and permanently lock their own BDAG. ChainPulse cannot access a user’s wallet or take coins automatically. The burn vault is public infrastructure and is not tied to a game or operator deposit.

Review verification record Verify deployed vault Download verified source v0.6.0

BlockDAG · Chain 1404 Ethereum · Mainnet BDAG vault verified · Ethereum anchor pending

CURRENT RESULT

Loading verification data

Checking the published evidence file.

Total publicly burned—Native BDAG · voluntary deposits only

BDAG network1404Branch pending verification

Ethereum evidenceMainnetChain ID 1

Verification stateCheckingFail-closed publication rule

THE SIMPLE VERSION

Three roles. Burned BDAG belongs to none of them.

The participant

Chooses an amount and confirms the irreversible transfer in their own wallet. Nobody else can start that transfer.

The ownerless vault

Receives native BDAG and has no owner, administrator, upgrade or withdrawal function. There is no key that can reopen it.

The evidence publishers

May approve and publish new documentation hashes on Ethereum. They can never control or recover BDAG held by the vault.

Why not 100 vault owners? Because a real permanent burn vault must have zero owners. Community voting and multisig approval belong only to governance and evidence publication.

VOLUNTARY PUBLIC BURN

Burn only what you choose.

LOCKED UNTIL VERIFIED

The vault accepts native BDAG only. A burn is permanent. ChainPulse never requests a seed phrase, private key or token approval.

Verified destination: Hidden until on-chain verification
Wallet account: Not connected

Activation follows only after the vault and Ethereum evidence are confirmed.

Your coins, your decision

Only the participant can approve and sign a transfer from their own wallet. ChainPulse has no collection permission.

Publicly documented

Every successful burn records sender, amount, optional reference and the vault’s new cumulative balance.

No operator deposit required

Deploying and operating the public vault does not require ChainPulse or its owner to burn privately held BDAG.

VERIFIABLE EVIDENCE

Every decisive claim has a public reference.

Run live vault verification

BDAG vault: Loading confirmed deployment
Vault deployment: Loading confirmed transaction
Vault runtime hash: Pending build verification
Branch reference: Pending independent RPC agreement
Ethereum anchor: Pending deployment
Ethereum transaction: Pending anchor transaction
Publication SHA-256: Pending final publication
Source manifest SHA-256: Loading source release
Source archive SHA-256: Loading source release
Verification report SHA-256: Loading source release
Public source: Pending public source URL

BRANCH SELECTION

One selected history, one documented conflict.

ENGINEERING LINEAGE SELECTED

Verified at 2026-09-13 15:35 UTC. The Engineering Explorer, RMS ChainPulse and WelshDAG independently returned the same selected hash at block 316002. BDAGScan and blockdag.works returned a conflicting history under the same Chain ID 1404 and are blocked for this deployment.

Endpoint	Observed head	Block 316002 hash
Engineering Explorer	Reference API	`0xcd4d2568e9cba6725329e8cf6d96217ace7acb03d71d9b519c8b2560bb6bb781`
RMS ChainPulse	21,091,933	`0xcd4d2568e9cba6725329e8cf6d96217ace7acb03d71d9b519c8b2560bb6bb781`
WelshDAG	21,091,931	`0xcd4d2568e9cba6725329e8cf6d96217ace7acb03d71d9b519c8b2560bb6bb781`
BDAGScan	18,491,894	`0xe2c7a9b0ff6206e6ac93f2cceead3992e081a4be64f5a5975d6e2158cc02a824`
blockdag.works	18,491,894	`0xe2c7a9b0ff6206e6ac93f2cceead3992e081a4be64f5a5975d6e2158cc02a824`

Release 0.5.0 selected the wrong history, was never deployed and is superseded. Before the successful Release 0.6.0 deployment, the complete zero-value creation bytecode was submitted to eth_estimateGas. Both Engineering RPCs accepted it with the same 139933-gas estimate, while the Engineering Explorer independently confirmed the reference hash. Open the corrected deployment preflight →

No withdrawal path

The vault has no owner, admin, multisig withdrawal, upgrade, external call or self-destruct mechanism.

Read vault source →

Exact-code verification

The deployed runtime must match the reproducible build byte for byte; appended Solidity metadata binds it to the exact source.

Open build hashes →

Cross-chain evidence

The final publication hash, vault address, code hash and branch fingerprint are anchored on Ethereum by the publication authority.

Read anchor source →

PRECISE MEANING OF “BURN”

Locked permanently, described accurately.

Native BDAG voluntarily sent to the vault becomes inaccessible under the published contract logic. This reduces spendable supply; it does not itself modify a protocol-level total-supply counter. The burn vault itself is not a multisig, because any withdrawal authority would contradict a permanent burn. Multisig governance may approve publication and Ethereum evidence, but it receives no access to burned BDAG. Public burn records rely on the matching vault event, never only a balance difference, because EVM value can sometimes be forced to an address without calling its receive function.

SOURCE RELEASE 0.6.0

Tamper-evident now. Ethereum anchoring next.

AUTOMATED CHECKS PASSED

A website can always be edited by its operator. This release therefore makes a narrower, verifiable promise: every source, document, test and build artifact is listed by exact size and SHA-256. Once the final publication hash is anchored on Ethereum, any later byte change is detectable. Corrections must use a new version and a new hash.

0111 / 11 tests

Vault, anchor, London-EVM deployment and public wallet safety executed independently.

02Two opcode parsers

Separate Node and Python scanners confirm no vault outflow path and no unsupported PUSH0.

03Two hash tools

Node plus POSIX sha256sum/OpenSSL accept the same 35-file manifest.

040 production findings

No production dependencies; remaining compiler-tool caveat is documented.

No third-party audit is claimed. The BDAG deployment and runtime are independently verified. An external security review and the final Ethereum publication anchor remain outstanding.

PUBLIC SOURCE DIRECTORY

Inspect everything offline.

Download complete package v0.6.0

SolidityBDAGBurnVault.sol SolidityChainpulsEvidenceAnchor.sol ReportTechnical audit HashesBuild summary DeploymentUnsigned zero-value transaction Live wallet codePublished wallet controller Independent codeFail-closed burn verifier Integrity35-file release manifest IntegritySHA256SUMS ProtocolMachine-readable verification Live RPC proofDeployment compatibility preflight On-chain proofConfirmed BDAG deployment PolicyVersion & immutability rules RunbookFail-closed deployment DocumentationGerman project guide SecuritySafety rules