Building in the shadows for a better future.
Relays (5)
- wss://relay.nostr.band/ – read & write
- wss://relay.damus.io/ – read & write
- wss://nostr.wine/ – write
- wss://nostr.bitcoiner.social/ – read & write
- wss://nostr-pub.wellorder.net/ – read & write
Recent Notes
The arkade sdks should have almost everything you need minus the web server for lnurl which is dead simple to build up. You don't set up your own arkd, you just implement a lightweight wallet and done! No api key needed.
Or you can use Arkade btcpay plugin and have btcpay give you ln address out of the box :)
I'd say beta or even ready to use entirely. Been trying it without issue for a while.
Its fiat, duh 🤣
https://plugin-builder.btcpayserver.org/public/plugins/stripe-paymentsFiatPay Server.
Ready for feedback and please leave a review and dm me with any issues encountered. 🫡
Feature is under development but a bit slow on this front. Stay tuned
This has always been the way. Hyping up "nostr" because "nostr" can only go so far.
It's the products that elevate any protocol beyond the nerd gaze
If it's monetary transactions that are the "problem", maybe the degen were right. How about pepe tokens pegged to 1 sat
Soon™️
Maybe I'll bring my copy and beg for an autograph🥺
No, this doesn't refer to the typical tps measurement used by blockchains.
I refer to the pragmatic upper bound for creation of new vtxos within a single onchain tx.
This bound is mostly defined by interactivity rounds between participants to construct the covenant. Since we do not have introspection covenants, we use a a series of n-of-n musig transactions. More vtxos = more interactivity.
We've had a functional ark for bitcoin for almost a year now, and since then we've optimized heavily along with plans to go even further. We have methods to achieve the above in concurrency, so that even with a single onchain transaction, we can create higher vtxo counts, without increasing interactivity for each VTXO owner.
In terms of "tps", I would say it is similar to lightning in that we have offchain instant transactions, but with actual transaction composability -- just craft a bitcoin transaction, sign, and submit.
There is of course no free lunch: one must swap their existing vtxos for new ones that are created with the commitment transaction (covenant session) described above, a trustless swap through connector outputs, for two reasons:
Batch expiries: these covenants have an expiry that allow the ark operator to reclaim its initial liquidity.
Switching from preconfirmation security (previous owner + ark operator collusion risk) to bitcoin finality (fully under your control). This also prunes the unilateral exit to a minimum tx set for broadcasting to.covnert vtxos to utxos.
