it's possible to spot such transactions if they violate transaction forwarding rules (aka standardness rules) but not consensus rules. for example, a transaction greater than 100kB is not standard but still valid.
Excited to see this new release. Seems to me this would (slightly?) negatively impact query performance for recent data (when the query concerns data is both in O3 and persisted zones), is that the case?
Proof-of-stake coins lack one of proof-of-work coins most important properties: censorship resistance.
In both consensus systems, a censor is someone that has amassed 51% of the currently available stake (in PoW stake is mining machines, in PoS it is outstanding tokens).
In proof-of-work systems, a censor can be unseated by censored parties allocating more capital to mining machines until non-censoring parties own 51% of all machines.
In proof-of-stake systems, it is impossible to unseat a censor: since it owns 51% of tokens, it will also owns 51% of newly minted units in perpetuity (assuming it doesn't stop censoring and doesn't run into issues that would end up slashing some of their stake).
USDT-USD markets are indeed marginal. however, implied USDT price using BTC as a cross shows USDT is valued pretty much at parity with the dollar by the market:
In some cases, increasing the fee once the transaction has been broadcast is not possible (original transaction doesn't use replace-by-fee OR child-pay-for-parent is not possible)
"miners somehowd eviate from the conventional wisdom or the norm, which dictates that transactions are prioritized for inclusion based on the fee-per-byte metric"
Miners prioritize by fee-per-byte, except that the on-chain fee only accounts for part of the fee paid for some transactions.
Over the years, many services have popped up where you can pay an out-of-band fee to a miner to include your transactions first.
Of course, this is detrimental to users not using these systems as it biases the algorithms used to determine what is the current best fee-per-byte to pay.
Using a full node, you not only sync the history, but also validate it. In recent days, on a modern machine with a good internet connection, it takes less than 12hrs to achieve this.
If you don't care about validating the history, I guess using BigQuery would work but I don't know how to achieve it.
- went back to the US several time after traveling to the DPRK despite being warned not to by the US state department
- had several consensual interviews with FBI agents
- consented to a search of his phone
It's hard to read this and not think that he brought this upon himself. If you really want to do what he did, get a lawyer, don't travel back to the US, don't speak to law enforcement.
How is the USD worth anything after some many bank robberies?
Bitcoin itself worked as expected, and the fact that no one can easily reverse transactions is one of the features described in the original whitepaper:
"Transactions that are computationally impractical to reverse would protect sellers from fraud, and routine escrow mechanisms could easily be implemented to protect buyers"
> What is it giving you that's worth the enormous montain of precaution that you need to take to secure yourself?
It's giving you precisely the opportunity the Binance hackers seized: doing transactions that no one else wants done. You don't have to ask permission nor trust anyone but Bitcoin itself.
It's funny that the USDC website doesn't list the main use of stablecoins (especially Tether) these days: arbitrage.
When moving fiat between two exchanges can take days and flag your accounts for suspicious activity, moving the same value using Tether is much much faster (~30 mins to 1 hour).
If one observes how does USDT flows, you'll find that it flows between the 3 or 4 major exchanges that use it, with almost no use elsewhere: no major wallets, no merchant acceptance, etc..
The real figure is more 2.1% (source: https://www.ssa.gov/oact/STATS/table4c6.html)