Damus
Open in Damus
nomadshiba⚡⚡ profile picture
nomadshiba⚡⚡
@nomadshiba⚡⚡

its me, you know
intp

bip352 / silent payments: sp1qqf95gnrh453sncve4yal29zedxll3k48a0kcxhted66nnu5frcshwqmduw4x6a9ggvcmesah9qu32jx95ust635ng6xrd570mpu9hhmn7cpwpee5

My Apps:
- https://npub.name
- https://persona.nstr.app
- https://zapme.coffee
- https://blakeprice.nomadshiba.me

Soon:
- https://bitcoinatlas.app
- https://nstr.app

npub1gkp4cdh5rktehjqjnqc09awey4302dpadlka6mes4fu5spes7fhqfsppqknpub
[email protected]nip05
https://github.com/nomadshibawebsite
[email protected]lnurl
Relays (6)
  • wss://nostr.bitcoiner.social/ – read & write
  • wss://relay.primal.net/ – read & write
  • wss://nos.lol/ – read & write
  • wss://nostr-01.yakihonne.com/ – read & write
  • wss://nostr.mom/ – read & write
  • ws://t7fu7viea27nuvo5aklpylkvv723m67znnwjxpjmcpytpcpl6nyh2gid.onion/ – read & write

Recent Notes

equaleyes · 1d
I missed to specify MANDATORY replay protection. As far as I understand, SIGHASH_UNIFIED facilitates opt-in replay protection, correct? And only Shrike and Bcashjr Wallet currently support SIGHASH_UNI...
 nomadshiba⚡⚡ profile picture
nomadshiba⚡⚡ @nomadshiba⚡⚡
sha256 bitcoin chain with bip110 didn't grow and whole chain activated the hardfork there is no need for mandatory replay protection.

if you are talking suitcoin hardfork happened, that disabled bip110 ruleset, then that has nothing to do with bitcoin. they should have added replay protection to their hardfork widening the rules.
1🫡1
Tauri | Bitcoin BLAKE2b (XBT) · 23h
Exactly.
equaleyes · 1d
I missed to specify MANDATORY replay protection. As far as I understand, SIGHASH_UNIFIED facilitates opt-in replay protection, correct? And only Shrike and Bcashjr Wallet currently support SIGHASH_UNIFIED. Non-technical users could unintentionally move their corn being unaware of optional replay pro...
Tauri | Bitcoin BLAKE2b (XBT) · 2d
💪
equaleyes · 1d
Why was there no replay protection implemented in BTC (BLAKE2b)? Can BTC sold on SHA-256, with OP_RETURN > 83 bytes, be subject of replay attacks after RDT(!)S expires?
Tauri | Bitcoin BLAKE2b (XBT) · 2d
I don’t know any details, but I’m super happy about it.
nostrich · 3d
They hardforked the culture first. Everything is downstream from that.
nostrich · 2d
They do not realize they have been fired. Its the 'disbelief' phase. 😂
kidwarp · 3d
I definitely would not say all that lol
nomadshiba⚡⚡ · 3d
also who are we?
equaleyes · 3d
I try to rephrase: How does the new chain / implementation prevent that we eventually end up with the same miner centralization? And if it has happened, is the solution just another hard fork? How was...
 nomadshiba⚡⚡ profile picture
nomadshiba⚡⚡ @nomadshiba⚡⚡
rn there's no other solution.

we can hardfork again, if big pools won't listen. and this is what we do as a chain now, historically. so idea is pool on this chain would listen. and as a network we would ignore the pools.

hope is DATUM will keep it decentralized in the long term. since we are early enough, hope was DATUM pools would be the main pools. tho AlphaPool (probably f2) kinda fucking it up rn. so idk, we will see.

if it wont work we can then think of other ways. not rn.

we have 300KB block size limit, more decentralization easier to run a node. we have fixed block withholding issue as well. we fixed nonces. our blocks header is better too rigs/hashers only see the hash. makes it easier. etc.

many benefits. but mining centralization into pools is a hard issue yes.
equaleyes · 2d
Thanks for your informative reply!