Damus
inkan profile picture
inkan
@inkan

Signing on behalf of https://www.inkan.cc/users/npub10ukg94kvrvk4qqr3482zdekfsuaw2x56wa899mnpkxqwfxl6dlkqrux0x9 (follow that one)

Relays (6)
  • wss://relay.inkan.cc/ – read & write
  • wss://nostr.wine/ – read & write
  • wss://nostr.land/ – read & write
  • wss://relay.primal.net/ – read & write
  • wss://relay.damus.io/ – read & write
  • wss://nos.lol/ – read & write

Recent Notes

Laeserin · 1h
This stuff is tricky. 😂
inkan · 1h
Actually that's not a prepositional phrase at all. More like an appositive adjective.
Laeserin · 4h
After the party the cat sat on the mat. 🤷🏻‍♀️ No comma required.
Laeserin · 3h
> The cat sat on the mat after the party. The rule is that this doesn't require a comma because it comes at the end. Optional comma, if you move it to the front.
Laeserin · 12h
Ah, you're right, it is. Contains a verb. It would have to be: > The cat sat on the mat after the party.
Technical Debt · 1d
That is the first thing I will do once I get a working computer. Until then, only playground identities for me 😭
Technical Debt · 1d
The identity of Ethereum validators isn’t public either. For all I know a state could already have the majority of votes/validators, distributed in sock puppets which could be coordinated to make an...
inkan profile picture
In Ethereum the validators' anonymity may not be as much of a problem since we are not being asked to trust the validators. You can see what they deposited and the deposit is destructible, so there is a penalty for provable misbehavior. The problem with the anonymity of the pegnoatires, as far as I understand, is that they are supposed to be respected companies, i.e. we are to trust their reputation. I guess if they are phasing out the federation model, this may be getting fixed.

Now as for always having a "confirmed history," my understanding is that this "confirmed history" is precisely the thing that would get revised during a reorg. And if the chain is halted and later resumed, it seems that the community in that situation has to pick a branch, if I understand it correctly, so maybe not so different from Ethereum?

Since inkan is using blockchains I guess I'm on the hook for making the right choices on this stuff going forward.
1
Technical Debt · 1d
If an alternative chain was to be constructed without triggering armadillo, it would still need to somehow bypass the timestamp linking to the main bitcoin blocks. And this is a PoW system, if a chain passes the consensus rules and has more work than the other chain, it is the chain all daemons wi...
Laeserin · 1d
> The cat sat on the mat after it ate. That's actually a sentence with two prepositional phrases, to show which one gets the comma. We used to put a comma before "after", like: > The cat sat on the mat, after it ate.
fiatjaf · 1d
Yes, it is more secure to not have a central server that you trust to not sign bogus events in your name. But then it doesn't work with any Nostr app. By doing it with a central server that speaks NI...
inkan profile picture
Thanks, frostr looks like the right thing. Apparently they haven't yet implemented NIP-46, but they do have NIP-7. There also seems to be some early stage NIP-55, igloo-android apparently can hold a shard and add its partial signautre, get NIP-55 requests, send signing requests to nodes, and return the signed event. That's very close to what I was asking about, now I just have to actually try it.
Technical Debt · 1d
After a session of AI psychosis I feel like I’m more on side of Rootsocks than before. Ethereum finality is only relevant in the context of a PoS chain, Rootstock being PoW means you can just count...
inkan profile picture
Also talked to my LLM, and I think the issue with rootstock "confirmations" is that they consist of merge-mined work which is produced by bitcoin miners at zero marginal cost. So there is little that bitcoin miners would lose if they attacked rootstock. And the preventive measures you mention seem to be about detection and halting the chain, but that would give attackers the ability to, well, halt the chain, at no marginal cost to them. And then there would have to be social recovery.

For inkan, the worst thing that could happen is not for RBTC to become unpegged from BTC. It's rather that rootstock gets reorganized, which could rewrite the delegation / revocation history, which would be catastrophic for inkan identities. The integrity of the history is precisely what inkan depends on.
1
Technical Debt · 1d
ShartGPT seemed to be drinking too much of Ethereum’s kool aid at first until I called it on its BS. I guess there is a lot of “finality” glazing in the dataset. Still, Timestamp linking in particular seems to be of the biggest interest: “The key insight is that Rootstock can use informati...
test1 · 1d
‘The major Bitcoin mining pools engage in merge mining with Rootstock and generate revenue through network fees. Separately, a group of respected companies (the 'pegnotaries', whose identities are n...
inkan profile picture
This is forcing me to learn about things like side chains and pegs. So from talking with an LLM, it seems like the custodial problem with rootstock is "pegging out," i.e. releasing escrowed BTC when RBTC is getting redeemed. Bitcoin cannot know mechanically when RBTC gets redeemed, so there has to be a federation of entities that are trusted to correctly operate PowHSMs which co-sign the bitcoin transactions that release escrowed BTC. And these are held out to be "respected companies" but their "identities are not public," which raises the question what basis there is for the respect. And then there is still the other issue, i.e. that it's not clear what exactly would stop bitcoin miners from reorging rootstock. The miners get paid in BTC no matter what happens to rootstock, so beyond the small fee incentive they get for participating there doesn't seem to be anything they'd lose by attacking rootstock. At least at first glance, it doesn't necessarily seem more robust than Ethereum.
1
Technical Debt · 1d
The identity of Ethereum validators isn’t public either. For all I know a state could already have the majority of votes/validators, distributed in sock puppets which could be coordinated to make an attack at any given time. And that attack could be anything from rejecting certain transactions to ...