@shadders is on PowPing!

PowPing is a place where you can earn Bitcoin simply by socializing, for FREE.
Never tried Bitcoin? It's OK! Just come, socialize, and earn Bitcoin.
Check out shadders's activities
Total Economy: 0.4 USD
A big day for SV infrastructure. https://bitcoinsv.io/2020/09/16/bitcoin-sv-node-software-important-upgrade-to-v1-0-5/ Bitcoin SV 1.0.5 'Rails' release is out today - Journalling block assember - batch sendrawtransaction - free consolidation transactions - lowered dust limit by 75% https://bitcoinsv.io/2020/09/16/mapi-v1-1-release/ mAPI 1.1 also released (formerly known as Merchant API) - batch transaction submissions for high volume users that want to avoid round trip latency. I published an explanation of consolidation transactions and how they enable the rise of nanoservices: https://bitcoinsv.io/2020/09/16/beyond-micropayments-the-rise-of-nano-services/
varaha tipped:
0.03 USD
1 year ago
benjamin tipped:
0.01 USD
1 year ago
venezia tipped:
0.01 USD
1 year ago
freddy78 tipped:
0.02 USD
1 year ago
lukz tipped:
0.11 USD
1 year ago
marquee tipped:
0.12 USD
1 year ago
token_squatting tipped:
0.02 USD
1 year ago
pete tipped:
0.06 USD
1 year ago
I can't quite figure out why he is going on a lengthy thread comparing these rails against Schnorr signatures... Am I missing the obvious analogy? https://twitter.com/pd_myers/status/1306361380333813760?s=20
token_squatting replied:
Upon reading the rest of the thread, it looks like he's doing it to trash BSV and call BTC Core geniuses.
benjamin replied:
Oh yeah, he hates BSV big-time... I just didn't really follow the logic of the comparison of those specific developments at all...
cog replied:
There is nothing to compare, he is just going for a dunk.
shadders replied:
He seems to be making the case that core good because they've. Implemented very complex algorithms to seemingly tackle a similar problem. Leaving aside the fact that the use cases enabled by both features are actually quite different. From an engineering perspective simplicity is always the preferable choice. It mitigates risk and keeps future support costs down. If one of my engineers came to me with a complex solution to a simple problem I'd send them back to start again (fortunately our people are way too experienced to ever do that). I think what this thread highlights is just how simple bitcoin can be when you lose the fear of using a few extra bytes. There is no need to create an impenetrable veil of algorithmic mysticism unless you want to empower a high priesthood of Devs who are the only ones that can decode it. Remember how the printing press disempowered the clergy by taking away their monopoly on knowledge and giving the power to read and write to the unwashed masses? Bitcoin is the next printing press. Its just a bigger, better version.
benjamin tipped:
0.05 USD
1 year ago
hermes replied:
"this thread highlights is just how simple bitcoin can be when you lose the fear of using a few extra bytes. There is no need to create an impenetrable veil of algorithmic mysticism unless you want to empower a high priesthood of Devs who are the only ones that can decode it. " Great explanation! ✌
Question: @shadders how are you pronouncing mAPI at nChain? Is it "May-Pee-Aye", or "Map-E", or the letters M A P I ?
benjamin tipped:
0.01 USD
1 year ago
benjamin replied:
Love it - the really important questions. I still feel uncertain every time I say gif...
shadders replied:
Haha, don't let's start the GIF/JIF debate :) I personally use both em-ay pi ay with emphasis on em. And map-e if I'm in a hurry...
turn up
This is awesome. Also super well written!
Thank you and SV node team for this great work! The link in "mAPI v1.1 Release" is broken, should be https://github.com/bitcoin-sv-specs/brfc-merchantapi/tree/v1.1#submit-multiple-transactions
hammerbrook tipped:
0.01 USD
1 year ago
shadders replied:
thanks for spotting this... fixed.
Great work!