@Truthcoin@saylor
1. Miners accept a set of valid blocks A
2. Miners accept a set of valid blocks B where B ⊂ A
B is a soft fork. The set of all possible next blocks has shrinked because we tightened (added) new rules/constraints.
@robin_linus@the_ecash@bergealex4 Maybe I'm understanding it wrong, but I think Peter's comment only says "we shouldn't do zk txs on the bitcoin mainnet". In other words, a zk tx error should not be a bitcoin mainnet error. It says nothing about doing or not doing it over bridges in a liquid-like style.
@robin_linus@the_ecash@bergealex4 One results in a broken BTC mainnet and the other in a broken chain that BTC (ideally) doesn't even know exists. Why would it be a good idea to add all the circuit complexity to the main protocol and not use layers and bridges to do composition and jumping between the two pools?
@robin_linus@bergealex4 A bridge can track the number of coins that get sent over which prevents the inflation catastrophe leaking to the Bitcoin mainnet. It can only ever be a problem on the other side and never on the Bitcoin network itself.
1/ Kudos for transparency. This is pretty much the worst possible bug for zcash, but it was found by a white hat (and hopefully nobody else before them).
From my understanding, the mitigation to potential inflation will be a jump of coins from a vulnerable pool to a secure one.
2/ IIRC the jump can control how many coins enter the new pool so you can prevent inflation leaking to the new pool. This also means that if the mainnet was exploited, some users could be unable to transition to the new shielded pool which could make exploitation detectable.
@satsammler@adam3us@Princey21M It would have become way less popular if you sent the whole file. Bittorrent works so good because you start downloading a single file from multiple people (peers) at once. Even BTTv1 sends you a sequence of sha1 hashes (BEP-3) to verify each chunk.
This guy is based and grounded in reality.
This is what happens when you maximize how courteously you treat murderers instead of maximizing how effectively you protect innocent lives.
Enough is enough - a deep line needs to be drawn in the sand. Talk is weak. Britain needs to say no more, and mean it.
A Restore Britain Government, with the British people's approval, would put Vickrum Digwa to death.
Henry Nowak was stabbed by Digwa five times, including twice in the back of his legs, once in the face and a fatal wound to the chest.
Rather than calling an ambulance, Digwa filmed Henry.
Digwa gave the knife to his mother and it was found by police at their home along with more than 20 other weapons.
Keeping this savage alive serves nobody.
The police officers on the scene who allowed Henry to die will face criminal charges for gross negligence manslaughter.
Digwa's foreign family will be deported.
Laws will change, the country will change, everything will change.
Order will be restored, the law will be restored.
Britain will be restored.
@Rob1Ham Even privacy coins have an audit of the supply. For instance Confidential Transactions check each transaction for inflation which the same kind of audit as Bitcoin does. The difference is in how easy/hard it is to find a faulty audit check and fix it.
The EU age verification app is presented as “completely anonymous”. But the risk is that member states (the countries are supposed to create their own versions of the open-source EU app) use it to introduce identity verification that makes it impossible to post anonymously on social media.
The idea behind “completely anonymous” is to use Zero-Knowledge Proof (ZKP) cryptography to break the link between the age credential issuer (EU governments) and the regulated services/sites. Currently, the EU app does not have ZKP functionality, contrasting Ursula von der Leyen’s claim that the app ”is technically ready to be used”. But more importantly, the app is designed to always function without ZKP technology; if ZKP is unavailable, the app falls back to a non-ZKP model. Even if fully developed ZKP technology could be implemented in the future, it would remain an optional extra feature that countries may choose to disable and that the EU could remove at any time.
This means that the EU could decide at any time that ZKP may no longer be used, and in one stroke the app would fall back to its default mode, meaning that every post on social media carries an ID tag. By that point, an infrastructure will already have been rolled out; people will have gotten used to it, and it will be harder to roll it back.
More details on https://t.co/wTVKHMS1zg
@exitnode_@ambimorph > Monero: Links -> untraceable
Any link is a potential trace. Thus the only way something can be untraceable is when there are no links at all.
That said, you can layer privacy on top the same way HTTPS does it. Instead of publishing/communicating X you publish ENC(X).
In 2017 we had many talks about how Smart Contracts would be used. A common example was literal contracts on chain, like a car insurance smart contract that pays the other side. That obviously didn't make any sense, and I argued that smart contracts are not for people. My counter example was autonomous cars making agreements on a parking lot about which spot to take. I.e., agreements between machines.
Not about money at all. It was before DeFi so we didn't see that path.
And I still think that's the way. Maybe not autonomous cars, but other machines.
The AI.
This thing can write, read and perfectly understand all the tiny details of a smart contract. So if an AI needs to make an agreement with another AI - they could collaborate on the code, deploy and execute what works for them. And no one can stop them.
@splix Every now and then I remember the talk you gave on this topic. I thought you were right back then, but it's a lot more obvious today now with the "rise of the machines". Frictionless JIT global agreements almost require us to remove humans. We are too slow and love friction lol.
@aBlock0@giacomozucco@peterktodd No, you have many different privacy vectors. Even zcash leaks transactions (and their timing), they're just encrypted. And while this is interesting, it can't scale and thus the only solution that scales is to have transactions for which a node can't even tell they happened.
@1HowardWu If our transactions blind the amounts with perfectly hiding commitments (Pedersen) then even a quantum computer would not be able to tell what value they hide. A QC could open the commitment to any value, but they wouldn't be able to tell what value was there originally.