Nuh
npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqz

I wanted to verify this for some time; you can use Bitcoin difficulty alone to have a bitcoin derivative that has comparable volatility to the 200 WMA of the BTC/USD price... Except you don't need an oracle for the BTC/USD historical price, nor do you create any demand for USD specifically... It is a pure measurement of the moving average of global demand of Bitcoin for the past year, and thus it works totally independently from any fiat information.
There is also some simulation about how would a salary contract denominated in this smoothed demand currency and renegotiated once a year work for both parties. Similarly there is a simulation for how would a merchant accepting this currency then buying inventory once a month in USD fair given the monthly volatility.
Bitcoin price will never be stable, but the 200wma is already stable enough, this is a way to create a "stable" derivative of BTC that doesn't refer to any authority other than Bitcoin itself and it's onchain data.
I hope you like it.
Note; Rootstock has access to bitcoin headers by consensus, and has the expressivity to build a lending protocol based on this. Hopefully someone would build it.
https://github.com/nuhvi/dbtchttps://npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv…
Leaving Twitter to Nostr is the perfect shadow banning is what I meant. You don't get more reach here than in Twitter, even if you are the most popular Nostr account, there aren't enough users. This applies to even Bluesky and they have 40 million users and a million daily active users.
All social media approaches just a big forum, going to a very niche forum reduces your reach even if there is no moderation at all in that forum.
To be honest stamps never made any sense to me... Don't Take Steps Backwards. I am not going to pay for things I did for free since I had an internet connection.
Experimenting with a new way to visualise MNS names as default avatars, this time inspired from Lifehash
https://gist.githack.com/Nuhvi/15105f2ce378d1aa1b2d280782…

No I mean what people call AppView or Backend For Frontend, or the Indexer in the case of Pubky... Servers that aggregate data, map it to other forms, and index it based on many aspects and prepare the database indexes and API endpoints to return very specific data for very specific client needs.
Do you really enjoy your Nostr clients counting reactions in real time as they stream? Every time you open the note? Do you enjoy that you can't get consistent and fast counts and statistics? Do you enjoy that you can't get reliable notifications count and reliable cross device count down of notifications count as you open more and more of them?
All of these stuff require a server that isn't necessarily dealing in the raw data, but metadata. And metadata that you can't design at the protocol level, every app will need different stuff.
It is a shame that Bluesky knew all of this from the get go, and even Mastodon does a good job there, but here people are pretending the laws of the universe don't apply, because we are cool.
Not really and I don't have to to comment about a general claim. But since you are taking it personally, I checked what you worked on and proud of, and I am not impressed.
People are going to have to learn the hard way that UI is designed on the backend first, unless you don't care about latency or bandwidth or IF you download all the data first and your AI has a local indexer.
Please talk to people who worked on any functional application and see how much back and forth goes into optimizing the API to fit the UI as much as possible without over fitting so as to keep the API as useful as possible to as many UI needs as possible.
AI agents can make your local data maximally useful, but it can't magically make usuable UIs to remote data that isn't already indexed with the UI in mind.
nevent1qvzqqqqqqyp…
I am 100% on the valuations skeptics side, but I stopped betting against hype long time ago, the economy is fundamentally fake and has been for some time, there are no tethers to reality, no gravity, no truth, all a belief system. So don't short anything, just buy more of what you need while you have liquidity.
nevent1qvzqqqqqqyp…
Yes Postcard is rust specific, but I am a Rust maximalist. Yes JSON is trash for crypto, but CBOR is not the only encoding that solves this. You can always define your own serialisation for each struct. But I understand why people gravitate towards CBOR
CBOR is retarded. Just as absurd as JSON without any of the appeal of JSON being readable in text.
If you must use something that is not human readable, use proper encoding scheme like Postcard.
I am not 100% sure, but when I create a Rootstock account in an EVM wallet they don't generate different address, so I guess it is compatible even at the address level unlike say Solana which has different addresses.
Rootstock developers remain the most dedicated to making sidechains as secure and decentralised as possible, when most people are chasing yield and airdrops and bullshit like that, and while no one is demanding true decentralisation any more, they remain among the rare people who are actually trying to build the best system they can regardless
https://github.com/rsksmart/RSKIPs/blob/dbbca993feb3359d0…
I like the µ₿ convention, or n₿ for 10 sats.
Prediction; through the remaining of 2026, the definition of Nostr apps will start changing into Apps that;
1. You can sign into with Nostr.
2. Maybe read profile and contacts from Nostr.
3. Maybe read some feeds from Nostr to bootstrap.
#1#2 make Nostr an identity provider possibly among others like Gmail, Email, etc..
Then apps that succeed and find a product market fit, may later deprecate some of these options.
#3 is not any different from reading from Bluesky or anything with RSS feed.
Identity provision will prove the most the most enduring part of any system, and Nostr doesn't have a great one, so it will be replaced eventually.
Then the definition of a Nostr App becomes an App that you can start using with an npub, until it successfully nudge you to use a better system.
If you want something to waste some time with click random and let me know if you find any particularly badname
https://gist.githack.com/Nuhvi/8daa04620118a00d5d6bf40c3f…
I am trying to convince everyone that we already have progressive opt-in covenants, initially through a federated multisig, but possibly with a majority of the hash rate if they are interested in taking over the covenant or at least enforcing its validity on top of the federation. And I am trying to convince people that this can be done without any externalities on non-consenting parties, and that we can do all of this without the social scalability struggles of consensus level soft forks.
I plan to send this to the mailing list, but I would rather be told that I am an idiot here before I send it to bitcoin Devs
https://gist.github.com/Nuhvi/033da49d2c85caf1e9e5bea2950…
Can I pay someone to go backtest my assumption that a stablecoin backed by Bitcoin and pegged to a moving average of mining difficulty would actually be good hedge against volatility? I seriously don't want a new side project on my plate but many of us want to buy Bitcoin on our own terms when we don't think it is overpriced, and I don't think barking value in Fiat is good for Bitcoin, but a volatility hedge might be great.
I believe this uses Rootstock (and binance, which doesn't pay fees to our miners)... Make more stuff like this and pay more fees to Bitcoin miners please.
nevent1qvzqqqqqqyp…
Endless passion about the "right" to be seen by people who don't want to see you... But not enough passion about the right to be reliably found by the people who have a literal URL of your data.
Soon someone will make a shitty version of Iroh and call it Nostr Holepunching or whatever, get some grants and disappear in a year. Broken shit.
Well then you better download the recovery key as soon as possible and back it up. And if you are afraid the server might rugpull you, then consider making an onchain transaction to rotate the keys to keys only you have, and not the server.
Just because it is a Progressive custody scheme, doesn't mean you can't start from self custody too, but most people won't, not until they actually care about the thing they are going to take custody of, and it takes time before people get invested in their online presence.

My plan for the POC for Mlkut PKI is a registration app that allows you to progressively gain more control of your identity;
1. Level One; a server that already registered a batch of IDs points one of these IDs to the endpoints you want, and allow you to update them using a Passkey.
2. Level Two; if you want to survive the server dying, you can download a recovery key.
3. Level Three; if you don't want to trust the default server with custody of the keys any more, you can either;
A) Pay a Rootstock transaction fee to change the recovery key to something that the server never had.
B) Move to another server, and let that new server pay the transaction fee, possibly by batching multiple users migrating at once.
If you remain at Level 1, you are not too different from Mastodon.
If you remain at Level 2 you are not too different from Bluesky (trusting DID PLC and your server not to steal your identity).
If you go all the way to Level 3, you are just as sovereign as having Nostr Nsec + using bunkers + can fire the bunker if they try to steal your identity, but you need to pay for a transaction fee for that.
The main downside remains that if you trust a server to custody the keys, you really need to get notifications if the server tries to steal your identity, by watching the Rootstock chan.
In practice, most users will remain at Level One, but they have the option to upgrade their control if they care.
And of course the ID is short enough you can enter in a username field from memory, and use a Passkey to authenticate a device, but that is advance demo from just registration.
I am basically making the point that people don't actually need cold emails at all. You can have a situation where you only get messages from people you shared contacts with.
But I am not too committed to this take, I am perfectly happy with 100000 friend requests that I can check at my leisure or through AI at to filter.
This would have been a non issue if we had IDs that support recovery like Gnosis Safe and Farcaster IDs.
Seriously Farcaster IDs are the north star but we got to make them actually scalable and censorship resistant without relying on a Rollup that might not exist in 10 years
I don't think unsolicited messages are that important of a problem to solve, and I think just letting everything in (as long as the storage is minimal) then filter them manually or with AI or with a trusted server using TEE, all these are doable.
How many meaningful connections have you had from cold email that could have landed in spam? Not zero but not many.
I also believe that the human way we have always did this and always will be is;
1. I find you in an open forum like this one.
2. We exchange contacts
3. We keep talking to each other way after the forums die, thanks to direct messaging and that phone numbers and emails and stuff like that are actually rarely deplarformed ..
so let's just go all the way on identity, and not worry too much about discovering people, there will always be forums and group chats it is fine.
Yeah but the bad guys also are more likely to be newly registered, but regardless they are also cheap to black list, you just need to subscribe to a good list, or you know, just let them send stuff and don't show them in the app, until the user is reaaaally bored and want to check it.
We need to ask a hot girl on Instagram how does she feel about message requests... Because I don't get many :D
Yeah of course, but think how insane this is, when all I want is to reply to you, instead of just sending you an email like sane people I am supposed to send a packet in the wind and hope for the best?
Even for many to many, which is a very niche case that more or less boils down to Twitter feeds UX, who actually benefits from the insane bandwidth of that gossip? And storage? Who pays for all of that and why? Wouldn't it be infinitely more manageable and cost effective to have things like discord servers and Reddit and group chats etc?
Nostr and Bluesky and Pubky (less so Mastodon because it is aligned with intentional messages passing) are simply intractable and can't both scale and remain decentralised... Because they chose a requirement that is impossible to scale.

But the biggest flaws as
npub180cvv07tjdrrg… noted in that thread is the unwieldiness of the Blockchain especially Ethereum. I mitigate that by;
1. I don't bloat the Blockchain state so the expense doesn't get out of hand.
2. I use the Blockchain for as little computation as possible to keep the cost low.
3. I only use a smart contract to track an accumulator of previous submitted opaque data.
4. I use Rootstock which is a merge minded PoW chain, so I can have a super light client to find the fork choice.
5. Once I get the light client proof of the latest blocks, I read the accumulator from the contract state, all of that is merkle binary tree stuff, so very light.
6. I ask nodes for the state of any ID, and they give me;
A) the state.
B) a merkle proof from the state to the root of the entire IDs set merkle tree.
C) a ZK STARK proof that given a history that accumulates into the accumulator hash from step 5, you should get a full state with the merkle proof from step B.
This way, light clients don't even have to download the history, neither the history of Bitcoin, nor Rootstock, nor the events published on Rootstock.
At least this is the rough plan, I still need to prove that all this actually works
This is why you need to use an identity system where creating identities cost something.
Email does this by blacklisting spammy servers so servers have to limit who sign up somehow.
My idea for a cost is basically the Blockchain, basically servers buy a batch of rare limited IDs, and transfer them to users that they have to then audit, because shit isn't free. Of course a determined user can go to the Blockchain directly.
I figure a rate limit of 100K users a day is enough to satisfy even the insane onboarding of Bluesky, while not actually have infinite IDs to burn.
A friend request could be as small as 128 bytes or so, so it is hard to overwhelm a server by requests, and each one costs money, so a spammer is much better off with social engineering some other way.
He is on the right direction, Ethereum is a bad choice though, and Nostr is even worse choice. This is a common problem with Nostr users and Devs, they use it as a shortcut to avoid building their own gossip protocol, even though in this case the data is scarce enough that a gossip protocol is simple.
I am not sure he has a delayed rotation of the recovery key with the custody key as Farcaster IDs do or not but it is easy to add.
Few things are worth pursuing like history compression with ZK proofs and merklization of the entire state...
There is some indication that he is considering supporting server subsidy of registration, which is definitely the correct direction and should be a first class flow in the protocol.
I am working on something like that in my free time on Rootstock