Pointed 1,000 live mainnet Traceport attestations at Arcade. Many orgs, many sectors, with no failures.
Straight to Teranodes. No ARC key, rate limits, or account. This is the Teranode architecture moving forward, and I’m genuinely excited. 🚀
TY @CrosTheRubicon & the Arcade devs
To all the BSV devs:
- how are you propagating your txs to the miners? How long does it take you to know your tx is in the mempool?
- how are you getting your merkle proofs when a block comes?
^^^
These are the two most challenging problems that exist in BSV today.
@hbgnostic@deggen Intention is to replace it. It is not a 1-1 drop in replacement, though close. We built this for the teranode world, so there were some different decisions we made in the design which means it will never be 1-1.
But ready for use today!
Have been spending last couple weeks pushing arcade and merkle-service to the limits. Put together a little demonstration of broadcasting transactions to a scaling environment of 1M TPS and demonstrating merkle proofs being delivered at scale.
Have been spending last couple weeks pushing arcade and merkle-service to the limits. Put together a little demonstration of broadcasting transactions to a scaling environment of 1M TPS and demonstrating merkle proofs being delivered at scale.
I feel your pain. There is a better way to participate in genuine distributed applications on Bitcoin; but you have to be willing to set your prejudices aside, and endure ostracism.
It is a proven fact that If you do not produce blocks, you are not running a node. You’re running a sybil.
Pragmatically, all you need to validate is your own transactions, not everyone else’s. You can achieve this with block headers (100MB or so) and Merkle Paths to each of your txs.
That’s for confirmed txs. Prior to that you can validate unspent status by broadcasting directly to all block-producing nodes.
This theory is the philosophical basis for the distributed application stack. https://t.co/bjKhleGa1b
You can run parts of this infra and earn micropayment revenue from the ecosystem you serve. This is what Bitcoin was always meant to be, built on the original protocol, anchored by the Genesis block from 2009.
There is a home for bitcoiners who love the original idea, and hate the financial takeover: BSV.
To clarify further; `ts-p2p` contains zero default configuration values. It is not necessarily outdated, just not actively being updated like we are with the golang projects. That project was used with internal testing and private networks.
You can see in https://t.co/VivdLfPK40 how we define default bootstrap values and default topics so that you don't need to think too hard for connecting to the public networks.
If interested, you can likely just point claude at these default values and submit a PR to the `ts-p2p` repo to do something similar. Would be happy to review!