NextCash

I'd appreciate feedback on @CashNext wallet. I know the UX is still rough, but it is fully SPV and peer to peer, just without interoperability because I don't like many of the existing systems for BSV. It uses simple messaging funded directly by users and focuses more on requesting payments and fulfilling payment requests over sending unsolicited payments, because that is how merchants work. I'd be happy to test with you.

My service payment design that is already functioning for NextCash services and wallet: * Client registers with server using key and providing callback URL to establish 2 way communication. * Client authenticates with server using key. * Client either sends a request to the service that requires payment and receives a 402, or directly requests to make a payment. * The service sends a payment request to the client's callback URL. * The client completes the payment request via the 2 way communication. * The service verifies the payment with the network and updates the client balance and notifies the client via 2 way communication. * The client sends authenticated requests that use the balance. documents.nextcash.tech/

I need more people to test @CashNext wallet. I should be rolling out the headers service soon so the client side can monitor the chain, and verify proof of work and merkle paths.

The update should be available from the Play store now. It should show as version 0.1.3.

@CashNext is coming soon. I'm just ironing out some issues. It uses a mnemonic phrase with deterministic key generation so you can recover from a data loss and is built around peer to peer communication with open protocol services to promote competition and prevent dependency on any one company.

I implemented SPV from scratch. My implementation is @CashNext.

I am developing @CashNext full node implementation and Android true SPV wallet. We should at least use a different prefix. So the addresses are clearly marked as BSV. Original and cash address support this. I think I prefer cash address with bitcoinsv: prefix.

@CashNext connects directly to nodes with no server.

Do you mean just ancestor transactions of your transactions? If you actually mean "all", then that is basically more than most full nodes do. @CashNext has no predetermined nodes. It has several seed nodes to get it started, but it builds a list of nodes by asking nodes for IPs.

I agree. A "double spend" p2p message would help improve SPV 0 conf. @CashNext displays the number of nodes that have "accepted" the transaction. Which can be an indication if there is an attempted double spend. But several full nodes are required for good 0 conf

Can someone point me to some evidence that bloom filters can be reversed into addresses and transaction hashes? @CashNext only sends bloom filters to nodes, and the nodes are randomly selected. It does not send addresses to anyone.

Check out @CashNext. It has parallel validation and mempool acceptance. Graphene is on my to do list.

I wish someone would invest in @CashNext. 😁 And yes, I am very confident that this level of throughput can work. I have made many improvements directly for this in the past week. It requires many other nodes to be functioning properly, in order to test.