We might be witnessing the fall of Tether right now. Lots of coins moving out of exchanges and premium on BTC on bitfinex is high. If they get banking resolved it could restabilize, though.
I'm looking into backups atm. I wonder how to make "strong" pins to use for backup encryption, or if there's a better mechanism I could use to prevent use of backups when they fall into wrong hands.
What are the chances after the next HF a 120MB block will be mined?
shortly after, like in the coming weeks? 0% half a year after when the advantages are taken better care of and other bottlenecks solved? higher-than-0%
How about:
Distributing a tx with a fee and your ip address (in OP_RETURN). Then the server whitelists this ip for x hours? Could this work?
If done for a very short time, or for a limited number of requests, then yes. But it would also complicate the system and you'd have to pay and store data in the blockchain.
What about it? It was offered as a scaling solution, but the goalpost kept shifting. Those who looked carefully knew all along segwit would never solve scalability. Now everyone knows.
I'm curious what it was like for those of you involved during the block size debate. I wonder how the debate within BCH now compares. Does it have a similar feel?
Compared to today though, we have solutions actively working to hardfork, which means a solution will be made. It might not be the best one, but it will happen. Better than stagnation.
I'm curious what it was like for those of you involved during the block size debate. I wonder how the debate within BCH now compares. Does it have a similar feel?
the BCH "civil war" debate, feels very similar to the *early* blocksize debate. That is a good thing, during early blocksize debate multiple solutions were offered - but none taken.
And one doubt with the account removal demo: it's succesful but shouldn't the linked account disappear from the app? Or is designed to stay?
The delete action is a "request for removal", and it should ideally listen to the response, and if the service reports success it should remove from the app as well. Not yet implementd
And one doubt with the account removal demo: it's succesful but shouldn't the linked account disappear from the app? Or is designed to stay?
There are two types of actions. Service actions and User actions. User actions include delete, update, revoke and logout. These actions is intended to be initiated by the user locally.
And one doubt with the account removal demo: it's succesful but shouldn't the linked account disappear from the app? Or is designed to stay?
The account removal example is a bit ill-made, normally it would be the user that selects the account in the app, and asks to remove it, not the service provider. Let me explain:
About the metadata: if a disable the nickname metadata in the "logging into a website demo" the logging is successful. Shouldn't it throw an error message?
The nickname is listed as optional, so it is not required and can be omitted.
Only tried it with demo.cashid.info. The QR code reader works fine and quick, although it's the first time I see that interface
Would you say the interface is better, or worse, than what you're used to? Did you try anonymous accounts? have you tried disabling metadata? did you re-use identities?