Bitcoin Runes

$RUNESSolana

Checkedin 1m 08s · Oct 5, 17:27 UTC

RUNES is a Solana token linked to a launchpad and proposed burn-to-Bitcoin-Rune service, but no required product role for this particular token was established. Mint and freeze authorities are absent, and metadata is immutable. Testing confirmed client-side burn restrictions, while direct API inspection showed an inactive devnet/signet configuration, blank Rune and reserve fields, and zero reported deliveries. Burn delivery and reserve accounting could not be tested because the supplied mint was rejected; launch testing also remained inconclusive after transaction-effect verification was blocked. Reported liquidity is zero, and the website does not reference the supplied mint, limiting confidence in tradability and its connection to the service.

btcrunes.funproductC1

Destroy any Solana token and receive the same amount as a native Rune on Bitcoin, delivered to the address you choose. No bridge, no wrapped coin, nothing to claim later.

The site says users can destroy a listed Solana token and receive the same amount as a native Rune on Bitcoin, sent to a chosen address without bridging or a later claim.

UntestedNot tested this run. Checked against Wallet test

Testing was inconclusive: the supplied mint was rejected, preventing a burn and corresponding Bitcoin delivery verification.

To settle it: Attempt a supported-token burn and verify the resulting Bitcoin Rune delivery and amounts against the Solana burn and specified Taproot recipient.

Wallet test, inconclusive: The mint is RUNES with no mint/freeze authority, but the service config reports burn not live and blank mint/Rune/reserve values. The blocker is absence of a supported burnable token and disabled service, not evidence that delivery fails.

Skeptic: doubtful

A burn followed by release from a pre-funded reserve is technically possible, but the site’s own configuration says the service is not live and points to Solana devnet and Bitcoin signet, not a live mainnet service. The homepage also marks mainnet burn and Rune delivery evidence as pending. Thus the promised user delivery is not demonstrated as available now. [E1][E5]

btcrunes.funproductC2

Real, finalised, and never claimed before. Anything else is refused.

The site claims burns are checked for finality and uniqueness before release, and that circulating Rune supply equals verified burns.

UntestedNot tested this run. Checked against Wallet test

No eligible burn or delivery record was available to test finality, duplicate prevention, or supply equality.

To settle it: Compare the Solana burn transaction, its finality, and its uniqueness with the corresponding public reserve outflow and Bitcoin Rune delivery.

Wallet test, inconclusive: Finality and uniqueness are stated in the UI but were not demonstrable without an eligible burn. Proof examples say pending.

Skeptic: doubtful

Finality checks and preventing duplicate claims are implementable, but the site provides no live configuration or delivery records with which to verify that these checks operate. Its mainnet and forgery-refusal evidence is marked pending. The claimed supply equality also depends on complete accounting across both chains and a funded reserve, neither of which is established by the current state. [E1][E2][E5]

btcrunes.funproductC3

Each Rune's supply sits in one public reserve address and is released only against a verified burn.

The site says each Rune's supply is held at a public reserve address and released only against a verified burn, with deliveries batched every few minutes.

UntestedNot tested this run. Checked against Wallet test

No populated reserve address or delivery history was available; reserve backing, conditional releases, and batching could not be tested.

To settle it: Inspect the published reserve address, if provided, and compare its outflows with verified burn records and Bitcoin transactions.

Wallet test, inconclusive: No reserve address is published/populated in config; the public-reserve and batching claims cannot be tested absent one.

Skeptic: doubtful

A public reserve with batched releases is a feasible design, but the published configuration has blank reserve-address and Rune-ID fields and the registry records no deliveries. The claimed reserve and release process therefore is not substantiated as currently operating. [E1][E2][E5]

btcrunes.funproductC4

Only coins listed on this site can be burned. Minimum burn: 10,000 tokens.

The service limits burns to listed coins, requires at least 10,000 tokens, and specifies a Taproot Bitcoin address.

HeldHolds up against Wallet test

Wallet testing confirmed client-side rejection of unlisted mints, amounts below 10,000, and unsuitable Bitcoin addresses, not successful on-chain burn enforcement.

Wallet test, confirmed: UI rejected the mint as not launched/listed here, flagged invalid Taproot/network string and explicitly said the legacy address is not Taproot, and warned that 9,999 is below minimum. This confirms the requirements and client-side enforcement, not a successful burn.

Skeptic: plausible

Listing eligible tokens, setting a minimum amount, and requiring a Taproot address are ordinary implementable service rules; the homepage states these restrictions. This supports that the rules are presented, not that the inactive burn service enforces them live. [E5]

btcrunes.funproductC5

LAUNCH

The site says it offers token launches; its config says launchLive is true, while the site presents launch controls and a launches feed.

UntestedNot tested this run. Checked against Wallet test

Testing produced and approved a pump.fun transaction request, but budget exhaustion prevented verification of transaction effects and cluster; full launch functionality remains inconclusive.

To settle it: Use the launch interface and inspect whether a launch transaction is created and which Solana cluster it targets.

Wallet test, inconclusive: Request inspection showed pump.fun program invocation and token/account initialization, no external payments, simulated -0.00881912 SOL. The later balance read was 5 SOL/no tokens while history showed a successful transaction signature, but I could not inspect that transaction's effects or verify cluster. The launch action was attempted; post-transaction verification was blocked.

Skeptic: plausible

The homepage exposes launch controls and a launches feed, and the configuration sets launchLive to true. This supports the existence of a launch feature, but does not independently verify the feed’s market-cap figures or actual trading. [E1][E5]

btcrunes.fun/api/configproductC6

{"live":false,"solanaCluster":"devnet","mint":"","decimals":6,"minBurnRaw":"10000000000","ticker":"ETCH","runeName":"","btcNet":"signet","runeId":"","reserveAddress":"","launchLive":true}

The site configuration reports the burn service is not live, Solana is set to devnet, Bitcoin network to signet, and no mint, Rune name, Rune ID, or reserve address is populated.

HeldHolds up against Wallet test, Site capture

Direct API inspection confirmed the reported configuration, including inactive burn service, devnet/signet settings, blank mint/Rune/reserve fields, and launchLive=true; operational launch success is not established.

Wallet test, confirmed: Config reports live=false, solanaCluster=devnet, btcNet=signet, and blank mint/runeName/runeId/reserveAddress. Form said supplied mint was not launched here. The on-chain mint lookup identifies RUNES, but that does not populate this service config.

Skeptic: plausible

The configuration API directly reports live=false, Solana devnet, Bitcoin signet, and blank mint, Rune name, Rune ID, and reserve address fields. [E1]

btcrunes.fun/api/registryproductC7

{"delivered":"0","deliveries":0,"recent":[]}

The registry API currently reports zero delivered Rune amounts and zero deliveries.

HeldHolds up against Wallet test

Direct registry inspection returned zero delivered amounts, zero deliveries, and no recent records; this confirms the API response rather than independently audited Bitcoin totals.

Wallet test, confirmed: Response was delivered 0, deliveries 0, recent empty. With no delivered amount/records there was nothing to compare to Bitcoin transaction records.

Skeptic: plausible

The registry API directly reports zero delivered amount and zero deliveries. [E2]

btcrunes.funotherC8

ETCH Bitcoin A native Rune Yes, on Bitcoin Rune markets

The site compares its proposed Bitcoin Rune destination with other named projects and claims its Rune is tradeable today.

UntestedNot tested this run. Checked against Wallet test, Market

No independent Bitcoin Rune market listing or identifiable Rune was verified. Blank identifiers and zero reported deliveries do not alone disprove tradability.

To settle it: Check whether the identified Rune exists and has active markets on Bitcoin Rune marketplaces.

Wallet test, inconclusive: The UI assertion alone does not establish market existence or trading. No identified Rune and no delivery records were available for on-chain/market comparison.

Skeptic: doubtful

The homepage claims the Rune is tradeable on Bitcoin Rune markets, but the configuration supplies no Rune ID and the registry reports no deliveries. Those facts do not establish that this project’s Rune exists on mainnet or is currently tradeable. [E1][E2][E5]