But what is free about this? It asks me - in chinese - to register to get "3 credits" and uses nano banana in the background?
🔔 This profile hasn't been claimed yet. If this is your Nostr profile, you can claim it.
Edit
But what is free about this? It asks me - in chinese - to register to get "3 credits" and uses nano banana in the background?
For now, yes. But don't build tools that need low on chain fees cause one such tool can fill the blockchain if successful.
But it's not necessary to constantly update things all the time. Do it once per day and you're far ahead of the crowd.
I would be more worried about "Spark and the underlying Mercury protocol relies on Hardware Enclaves specifically Intel SGX." If the SE runs funds through some malicious Spark account, let's call them Eve, and monitor the SGX's memory for the supposedly destroyed SE keys, they can unilaterally exit with all your funds and there's nothing you can do to stop them.
Looks like spark uses a utxo model where your exit cost doesn't scale with the age (how many transactions) but the fragmentation of your utxo set. If you conslidate many spark balances in many costly UTXOs into a new one, previously owned by somebody else, you might need only 3 txs to exit or you might need 10txs per utxo if all the leaves you have from that Merkel tree are not deep neighbors.
You have my 2GB!
I'm all for that but suspect it can be compressed further and limiting to "follows of follows" or "follows of follows of follows" would spare you the bulk of reports as these are unconnected accounts. Find my follows. Find their follows. Find their follows. Find all the rest **by** and **about these pubkeys**. A report authored outside of that group is irrelevant. Pubkeys outside are "unknown". Reports by the in-group about them add little signal. A new spammer is "unknown" while an old spammer is known to be blocked. Hopefully we get heuristics about older accounts outside the group somehow but to give a new account some credit will only result in spam getting sent with only new accounts.
Losing 99.99% of its value is a very reliable heuristic to disregard a shitcoin as irrelevant. I never claimed the opposite was also true.
The X app is dispensable absolutely but what about your banking app and other stuff. One of my banking apps was telling me how to make it even easier enabling the front camera and I bet some months from now that won't be optional anymore. Sure, I can use another bank but banks tend to do these things and politicians tend to push them that way. And it's not about you and me. We might jump through hoops to live on a bitcoin standard but in a world where we are the unicorns that still use open tec. Bitcoin is dead. If people have to hunt old computers at garage sales to be self-sovereign, killing bitcoin becomes very feasible. Bitcoin needs pervasive open computing. Hardware-based attestations do not stand against that in principle but in practice it often does. A smart phone has many chips and one of those can be - decoupled from the main functioning of the device - provide attestations but if you want it to attest to the OS being locked down then ... well ... you run a locked down OS or don't have attestations.
In this space, the price is a great proxy for what's a good idea or not. I didn't need to know that "great for gpu miners" was their flaw but now that you told me it's clear why it didn't take off.
I'd like to add that the proposed scheme could be extended tapping into bip39 where we hashed 2048 times with PBKDF2, right? So if a wallet's failure to send all funds were your concern, this would allow to pre-image the pre-image many times.
I think it covers a tiny fraction of coins not protected due to early p2pk not being covered but if we decide to burn addresses that cannot plausibly be attributed to owners, bip32 has to constitute an exception.
Sorry, you've lost me. If the answer to your question happens to be the negative outcome, we are in peril, so it's not changing my assessment.
We can't afford to wait for it to break. CRQC would kill Bitcoin if it was real today. An attacker could manage to take most bitcoins while causing panick and a fee event that would generate weeks of mempool backlog, exposing even more coins.
I said it many times: clients should implement what fiatjaf called pet names. And the concept should include the avatar.
They'll take your coins and compensate you in paper.
https://walletscrutiny.com https://nostr.info Working on Bitcoin, Nostr and being a good dad.