$RUNESBitcoin Runes
- Metadata
- locked
- Update auth
- none
- Source
- token-2022
$RUNES
Bitcoin Runes
Done13/131m 08s
flags
- confirmed
- refuted
- untested
- unverifiable
- marketrule
No liquidity
Liquidity $0
Market
- deployerrule
Hub funded
Funded by a high-activity wallet
Neighborhood
- socialrule
X renamed
@TryBitcoinRunes changed its handle 1 time(s), last on 2026-09-22
X account
- socialrule
X renamed near launch
Last renamed 13 day(s) before the token was created
X account · Deployer
- siterule
Mint unreferenced
The address does not appear on https://btcrunes.fun/
Website · Site capture
- kind
Memecoin
No required fee, access, or other functional role for RUNES is established, and testing rejected the supplied mint as unlisted.
Metadata · Hands-on · site/mint-unreferenced
- product
Launchpad
Launch controls generated a wallet request invoking pump.fun and token initialization, although completed launch effects remain inconclusive.
Hands-on · C5 · Site capture
- product
Bridge
The proposed burn-and-reserve-release mechanism transfers token exposure from Solana to Bitcoin, functionally a cross-chain service despite its 'no bridge' wording.
C1 · C3 · Skeptic
- claims
Team anonymous
No team members are named in the reviewed material.
Site read
- site
Inconsistent claims
Operational delivery and current Bitcoin tradability language conflicts with inactive testnet configuration, blank Rune identifiers, and pending mainnet proof.
C1 · C6 · C8 · Site read · Skeptic
On-chain
$22.6kmarket cap
- Price
- $0.0000226
- Liquidity
- $0
- Vol 24h
- $73.9k
- Pool
- pumpfun · 15h ago
Fixedsupply
- Program
- spl-token-2022
- Supply
- 999.26M
- Mint auth
- revoked
- Freeze auth
- revoked
- Transfer fee
- none
- Extensions
- metadataPointer, tokenMetadata
34.1%held by top 10
15hsince launch
- Wallet
- Aqtg…VuRH
- Launched via
- pump.fun
- Created
- 2026-10-05
1/1sibling tokens dead
- Linked wallets
- 3
- Siblings > $1M
- 0
- Latest
- $PENNIED
Summary
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 (metadata; usage). Mint and freeze authorities are absent, and metadata is immutable (facts; metadata). 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 (usage; capture). 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 (market; website).
Claims 8
untested
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.
Testing was inconclusive: the supplied mint was rejected, preventing a burn and corresponding Bitcoin delivery verification.
untested
Real, finalised, and never claimed before. Anything else is refused.
No eligible burn or delivery record was available to test finality, duplicate prevention, or supply equality.
untested
Each Rune's supply sits in one public reserve address and is released only against a verified burn.
No populated reserve address or delivery history was available; reserve backing, conditional releases, and batching could not be tested.
confirmed
Only coins listed on this site can be burned. Minimum burn: 10,000 tokens.
Wallet testing confirmed client-side rejection of unlisted mints, amounts below 10,000, and unsuitable Bitcoin addresses, not successful on-chain burn enforcement.
untested
LAUNCH
Testing produced and approved a pump.fun transaction request, but budget exhaustion prevented verification of transaction effects and cluster; full launch functionality remains inconclusive.
confirmed
{"live":false,"solanaCluster":"devnet","mint":"","decimals":6,"minBurnRaw":"10000000000","ticker":"ETCH","runeName":"","btcNet":"signet","runeId":"","reserveAddress":"","launchLive":true}
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.
confirmed
{"delivered":"0","deliveries":0,"recent":[]}
Direct registry inspection returned zero delivered amounts, zero deliveries, and no recent records; this confirms the API response rather than independently audited Bitcoin totals.
untested
ETCH Bitcoin A native Rune Yes, on Bitcoin Rune markets
No independent Bitcoin Rune market listing or identifiable Rune was verified. Blank identifiers and zero reported deliveries do not alone disprove tradability.
Off-chain
@TryBitcoinRunesBitcoin Runes
- Renamed
- ×1 · 14d ago
- Account age
- 15d
- Based in
- Australia
btcrunes.funresolved
- Found via
- metadata
- Mint on site
- no
- Stack
- —
- Trackers
- 0
- Endpoints
- 4
- 3rd-party hosts
- 2
Bitcoin Runes presents itself as a Solana-to-Bitcoin Rune burn-and-release service: users burn listed Solana tokens and specify a Bitcoin Taproot address, with the site claiming an equal amount of native Rune is released from a reserve. The same site also displays token launches, but its exposed configuration reports the system is not live and uses Solana devnet and Bitcoin signet.
- Observations
- 4 · 3 concerns
- Claims judged
- 8 · 4 doubtful
- Looks like
- Bitcoin (unstated)
- journal
- Reviewed the burn, launch, and project-comparison pages; queried config and registry endpoints; checked the provided mint on-chain; and connected Phantom. Wallet initially held 5 SOL and no tokens. The burn form rejected the supplied mint and the unlisted test mint, enforced a 10,000 minimum, and rejected invalid/non-Taproot recipient examples, so no burn request or transaction existed for C1-C3. Config showed live:false, devnet/signet, and empty mint, Rune, and reserve values; registry returned zero deliveries. For the launch, filled a plausible test form, uploaded the test image, used zero initial buy, clicked launch, inspected the wallet request, and approved: request called pump.fun, showed token/account setup, no payments, simulated SOL decrease 0.00881912. A subsequent wallet balance still showed 5 SOL and no tokens; history returned a successful signature, but chain_transaction inspection was blocked by tool-budget exhaustion. Thus launch effect and target cluster remain unverified. No Bitcoin Rune identity/market could be checked because the config provides no Rune name or ID.