Bitcoin SV Node Q&A

Shouldn't this be updated (STN)? https://bitcoinscaling.io/tps-watch

Looks like @shadders posted the teaser for the Dynastic version of BitCoin SV (1.0.7) everywhere but @powping so here's the link: https://bitcoinsv.io/2020/12/24/a-belated-christmas-present-from-bitcoin-sv-team/ We'll pitch in where we add the most value: https://www.slictionary.com/testit/dynastic/055fd29d6baec07fd6d7cb243fa463ddb4801cb7832d624d830978b96e48bd2d

Because people keep asking for the source of the "ZSO"s. It wasn't a paper on ZSOs, but an overall release statement from nChain about the "Rails" update which has several facets-- including an exciting dust-collection method which allows "conservation of BitCoin"-- which sounds very appropriate and makes some economic sense as well. Here's the quote on ZSOs: "the creation of dust outputs themselves are still limited to some degree by the dust limit. This limit will be removed entirely by the

Maybe I'm being too much of a Spok here, @shadders , but this sentence's semantics beg for a question: "SPV Channels CE (for “community edition”) allows asynchronous encrypted messaging between participants, even when there’s no direct connection between them (e.g. one may be offline)." Does "direct cxn between them" mean: 1) The wallets can talk to each other, via something like NFC phone-to-phone, but niether can talk to the internet (no WIFI or LTE)? 2) One wallet can access the internet

Hello, will Chronicle hardfork be announced out of the blue, or there will be a preparation phase disclosed before to?

Can you fix this link @shadders? https://bitcoinsv.io/2020/05/15/bitcoin-svs-transaction-fee-economy-guidance-for-miners-and-application-developers/

What determines if Bitcoind "rolls forward" during a restart? Also what determines how far back it rolls forward? Not ideal not knowing how long a node restart will take in a live enviroment.

What’s the plan for unconfirmed chained transaction limit? TAAL has raised it to 50. https://coingeek.com/taal-lowers-bitcoin-sv-transaction-fees-to-support-enterprise-blockchain-applications

I'm running a Bitcoin SV Node in pruning mode and would like to get the UTXO from different addresses, I should have the utxo set in memory, is there an easy way (RPC Call?) to access?

The small blockers insist that really big blocks cannot possibly be propagated within the necessary time reliably. How does BSV Node plan to support "Tera" sized blocks? Are you guys planning to propagate meta info instead of full blocks?

There are a lot more would-be developers out in the woods. A guided educational roadmap similar to this is a MUST for Bitcoin SV to become more widely adapted. https://roadmap.sh/

is it correct that it is not possible for any miner to fork on the Bitcoin SV chain because of the "Open BSV License version 3"?

Hey @shadders thank you for being willing to answer questions about the Bitcoin SV node and BSV protocol. Do you think that BSV is controlled by anyone? This is in reference to the tweet I can only conceive of a reality where a select group of individuals have power to make changes and therefore could possibly pull an Amaury (no disrespect intended toward him). Are there mechanisms in BSV to prevent such control? I don't see any hap

Ok, so 0-value BSV tokens scare me, and so do OP_FALSE/RETURN unspendables. The first question is: Will Nodes be allowed to create their own private dust limits? Will they always have control over whether they allow 0-value tokens or not? Next question, just from thinking about it (no research), how hard would it be if in like 5 years BSV wanted to shift to 128-bit computing, and on top of that how hard would it be to allow decriminalization down below 8 places (to the right of the 1 bitco

Bounty to whoever can tell me when WOC or TAAL moves to 1.0.5 WOC is still on 1.0.4

welcome back to the future-->

Introducing Bitcoin SV Node Q&A channel for general bitcoin protocol discussion. Please take a look at the rules, they're pretty simple :) https://powping.com/c/d26dc10aed29226b36ef11938b0e2c7dbef055b81e4d83de73281a88515c9aa1