Community links, gathered.

An RPC supplies wallets and applications with blockchain data. A network name or chain ID can be copied, so those fields alone do not prove that two RPCs serve the same ledger.

Compare recent block hashes, transaction results, wallet balances, and peer connectivity. The AMAs report that the bdagscan endpoint did not match public mainnet RPCs. Because that claim is disputed, verify the difference against independent nodes rather than relying on either side’s description.

The same wallet address can show different balances when two RPCs return different transaction histories. A balance or transaction recorded on one ledger will not automatically appear on another.

Check the RPC address, latest block, transaction hash, and destination wallet when investigating a discrepancy.

A purchase, vesting entry, or claim recorded only in a presale or dashboard database is not an on-chain mainnet transaction. It cannot appear on mainnet without a valid mainnet distribution.

The 4 September AMA discusses possible future community remedies, such as a pooled allocation or distributor, but no funded or approved recovery programme was confirmed.

A native coin is built into a blockchain’s protocol rather than issued through a smart contract. BDAG is used to transfer value, pay gas, reward miners, and participate in staking on the BlockDAG network.

The 27 August AMA states that mainnet would continue in its existing form and that BDAG already recorded there did not require a swap or migration.

This was the position reported during those sessions. Any later protocol proposal would require current documentation and network adoption.

The 4 September AMA also reports that roughly 46 billion BDAG had not yet been issued and was assigned to the mining-emission schedule over approximately ninety years.

These are dated AMA figures, not a current audited supply report. Current totals should be checked against live network data.

The reward was described as following a declining emission schedule, with each block’s reward divided between mining and staking.

This is the allocation reported in the AMA. Current protocol settings and actual distributions should be checked against live chain and payout data.

A mainnet staking position is recorded in the staking contract. Its public interface can be called directly with the holder’s wallet, so a hosted dApp is not technically required.

Verify the current chain, contract address, transaction history, and instructions before signing. A record held only on another ledger does not automatically create a mainnet position.

Confirm the recipient address and network before sending anything. The wallet owner should sign their own claim, staking, or transfer transaction.

Do not connect wallets to unverified claim sites or sign unexplained approvals. The 4 September AMA reports that spoof sites had already been used to drain wallets.

Exchanges decide which RPC and ledger they support. A venue may pause transfers while it reviews network stability or reconciles conflicting RPC data.

Do not send mainnet BDAG to an exchange until that exchange confirms that deposits are open for the same network.

The reported integration estimate was five to ten days. That was an estimate given during the session, not a guaranteed launch date.

A listing should be treated as live only when the exchange publishes the supported network, ticker, deposit and withdrawal status, and opening date.

The AMAs discuss exchange pairs, partnerships, privately funded liquidity, and community-built DEX options. These were possible routes rather than completed services.

A usable DEX still requires deployed contracts, an interface, liquidity, and public verification.

The 27 August AMA links resumed miner sales to usable exchange listings and liquidity. The stated reason was that hardware should not be sold while buyers have no practical way to monetise mining rewards.

The AMA therefore gives a condition for restarting sales, not a fixed date.

Publishing a protocol update does not change the network by itself. Miners must install compatible software and direct hash power to the chain that follows those rules. If miners remain divided across incompatible rules, separate chains may continue.

No single miner controls the outcome; it depends on collective miner and network adoption.

The AMAs propose separate governance roles for stakers and miners. Stakers would vote through locked BDAG, while miners would participate through the infrastructure and hash power they operate.

The proposal still requires governance rules, contracts, custody controls, developer work, community review, and network adoption.

The AMAs state that no mainnet DAO treasury is currently receiving gas revenue. A future treasury would require a defined funding mechanism, transparent wallets, multisignature controls, spending authority, reporting, and community oversight.

Fees charged by an independent dApp are separate and follow that application’s own revenue model.

Developers can connect through a public RPC or operate their own node. Because BlockDAG supports the EVM, they can use compatible smart-contract and application-development tools.

A developer can deploy independently without waiting for a central team, DAO, or website administrator to approve the project.

The reported MVP included wallet and portfolio views, trading access, staking management, network access, and selected services. iOS and Android versions were also mentioned.

Testing, contract review, operational safeguards, community input, and production funding were still outstanding.

Planned content includes documentation, verified RPC endpoints, explorer links, test tools, SDKs, examples, contract information, and public network-status pages.

The portal was also discussed as a place for developers to publish proposals and find community support or funding.

The 27 August AMA states that external audits were not funded at that time and that vetted developers would perform internal reviews in the interim.

No external auditing firm, engagement date, completion date, or published audit report was identified.

Visualisation and dashboard software were expected first, followed by pool software after internal review. Core-chain source was expected later, after governance and community review were established.

These were planned stages, not confirmed releases.

The reported calculation was approximately 1.2 blocks per second with about 3,500 transactions per block. Peaks above 5,000 transactions per second and up to 1.6 blocks per second were also mentioned.

The AMAs do not include benchmark methodology, test conditions, raw results, or independent verification for these figures.

The 27 August AMA states that there were no verified investor commitments at that time. The later 4 September AMA does not announce one.

A credible confirmation would require a named investor and an official announcement from the investor or project.

The 27 August AMA states that the current community work was being funded independently and that its organisers had no access to the historical sale proceeds.

Control of those funds is disputed. The transcripts record the organisers’ account but do not independently prove who currently controls the proceeds or related wallets.