BIP300 and BIP301 go together.
BIP300 has new txn type and the messages processed by miners and any nodes wanting to track state (anyone participating in a sidechain enabled by drivechain would be interested in this for fund state). Message types 1-4 are OP_RETURN. Types 5 and 6 are the deposit and withdraw tx.
The tx are set as anyonecanspend, which necessitates economic majority nodes to enforce, not miners.
If miners implement support and changes to consensus rules without adequate social consensus, this would constitute an attack.
Layer 0 sets the rules, and consensus on drivechains hasnt been met yet
I liked it a lot. 8/10
Its the last TV show I committed to wstching as they had a planned duration from the get go and seemed safe from premature cancellation.
4, 8, 15, 16, 23, 42
Actually thats good feedback.
I look at it from the technical side and balancing privacy issues and segregating who has what data.
But for most orgs with paid recurring memberships, they dont necessarily have the technical desire to set all that up and would benefit from a turnkey solution.
So to that end, if theres enough demand I wouldnt be surprised to see nodeless put together something with a fee structure that takes into account both the receive and send tx for an invoice, but also the account service provided, management UI, and notifications sent to initiate the invoice
When did strike add the ability to request payment in sats as the denomination
This is a strike invoice
lnbc3690n1pjd67lvpp527xlg3ef6jm7fj8c0wp34ett8wx2t6gjmsxg6mf85cg7mgtjqn2qdqqcqzpgxqrrs0sp5xlrsvrcuvw7ngprxjkmg0nqqdamwm7uqr3yu7zkzsj08uj332g9q9qyyssqxeqx305z6vzj8rmq9a8qem2cqzqn2t5q86s63ntq0xfy3lzgs5ckeq6qhpstc32aafws6ca37m4jvxx7pyq3snrsnqmlv98rh7fn4lgpz4ta9j
Would be a worthwhile implementation pattern, though not sure Id want nodeless or any similar payment processor to have account info for contact (email, nostr, whatever), or the subscription details itself.
Better way to implement is as service that people can run on a vps so they maintain that data on their own and only call nodeless for generating invoice and relying on webhook. And then have daily check of accounts with subscription expiring soon and start notifying.
Would be a good hackathon project.
If I built something like this Id probably leverage AWS just for more expedient buildout and lower initial costs.
Discount for prepaid in advance for a year+, or else remind month to month or whatever frequency.
Subscriptions that rely on people forgetting their autopayments should be relegated as a bygone relic of a less sovereign age.
What stage is this of the 12 step program
Sounds like an evening with nostr:npub13wfgha67mdxall3gqp2hlln7tc4s03w4zqhe05v4t7fptpvnsgqs0z4fun
Offends PETA because cats, plus he ate one. Would probably be declared racist unless changed away from white suburban family. They would also need to change the interactions of the blind woman. Cant not have her as that would be both sexist and against people with disabilities.
Or we can accept that 3rd rock from the sun _was_ the variant reboot, and that too needs an update
New nostr post made β
Consider this an announcement of an announcement.
Whats the benefits of it?
