|
Remember this and only this...
This is the best coin out there. 21 M, directly tied to Bitcoin the ledger... Is mined, when Bitcoin the ledger, is not.
Combined with IXC = 42 million and 99.99% minted.
Secure, stable, and about to explode.
Only SSL patched crypto that would be compliant with new PCI DSS v 3.2.1 making it the only crypto allowed to be a Bitcoin Visa Debit Card. Would make instant adoption possible through anywhere Visa, MC, AmEx, Discover are accepted.
Do not be an idiot and have weak hands. This is imminent.
|
|
|
|
I see what you did there. Another EXCELLENT article, Dan the Man. xoxo, RV (oh I’m not sure I can get used to the motor home image, lol)  RV you brought this upon yourself. Few things - I wake up - some BS news. But if the future of Bitcoin is in payment - time to make heads spin and allow the TRUTH of just how exactly PCI DSS (your find btw) makes that possible for crypto! Excellent work on your behalf DT.  I’m glad I could have helped. Indeed time to make heads spin!!!  Show is over. Let the world find out they had 7 years. |
|
|
|
I see what you did there. Another EXCELLENT article, Dan the Man. xoxo, RV (oh I’m not sure I can get used to the motor home image, lol) RV you brought this upon yourself. Few things - I wake up - some BS news. But if the future of Bitcoin is in payment - time to make heads spin and allow the TRUTH of just how exactly PCI DSS (your find btw) makes that possible for crypto! |
|
|
|
This is the best coin out there. 21 M, directly tied to Bitcoin the ledger... Is mined, when Bitcoin the ledger, is not.
Combined with IXC = 42 million and 99.99% minted.
Secure, stable, and about to explode.
Only SSL patched crypto that would be compliant with new PCI DSS v 3.2.1 making it the only crypto allowed to be a Bitcoin Visa Debit Card. Would make instant adoption possible through anywhere Visa, MC, AmEx, Discover are accepted.
How can it be any clearer? Vlad, am I making sense?
Crystal clear to my ears. Post deserving of 7 merit points. 7 is a good number. Hopefully the rumors are true and we’ll get the truth by Saturday. Saturday being the 7th day of the week? Lukedashjr would disagree. Sunday is the 7th day of the week My Saturday is RV's Sunday. https://medium.com/@danieltreccia/bitmark-zuckerberg-5344282235d1D-Day: June 30, 2018. |
|
|
|
This is the best coin out there. 21 M, directly tied to Bitcoin the ledger... Is mined, when Bitcoin the ledger, is not.
Combined with IXC = 42 million and 99.99% minted.
Secure, stable, and about to explode.
Only SSL patched crypto that would be compliant with new PCI DSS v 3.2.1 making it the only crypto allowed to be a Bitcoin Visa Debit Card. Would make instant adoption possible through anywhere Visa, MC, AmEx, Discover are accepted.
How can it be any clearer? Vlad, am I making sense?
Crystal clear to my ears. Post deserving of 7 merit points. 7 is a good number. Hopefully the rumors are true and we’ll get the truth by Saturday. Saturday being the 7th day of the week? |
|
|
|
|
This is the best coin out there. 21 M, directly tied to Bitcoin the ledger... Is mined, when Bitcoin the ledger, is not.
Combined with IXC = 42 million and 99.99% minted.
Secure, stable, and about to explode.
Only SSL patched crypto that would be compliant with new PCI DSS v 3.2.1 making it the only crypto allowed to be a Bitcoin Visa Debit Card. Would make instant adoption possible through anywhere Visa, MC, AmEx, Discover are accepted.
How can it be any clearer? Vlad, am I making sense?
|
|
|
|
Treccia I read in your article about the possibility of the BTC not reorganize properly, what would happen? NLX plans the testnet with zeroprotocol in Q3, which started exactly in 3 days... After that, what else is missing? Will ETC start operations on coinbase and wall street arrive?
I don't know if you're alluding to state reorganization but my main point is everything will lead to that. After reorganization things will be fully functioning and code will be correctly encoded and decoded in a way that smoothly functions for future use of the blockchain. |
|
|
|
(sorry to keep going off-topic on I0coin)
But, my theory is this:
Someone is doing testing or has deployed, or is in the process of deploying, a large amount of ASIC using covert asic BOOST. Reasons being:
1. Sudden large increase of hash power and diff on Bitcoin and Merged-mined BTC coins
2. Empty/small size blocks
- Empty blocks being added to BTC's chain
- Small block sizes
Mining empty blocks and small blocks are clues that covert asic boost is in use. Covert asic boost
"Miners must look for one collision of 4 bytes, which is 32 bits — so this collision is one of 232 hashing attempts. We take the square root this due to the birthday paradox to arrive at a n approximate expected total of 65,536 attempts.
Each attempt may require changing the extra nonce to generate a new Merkle root hash. However, due to the structure of the Merkle tree, this would require even more additional hashing. If we change the extra nonce, a new is hash is required for each row of the Merkle tree. For a large Bitcoin block with perhaps 10 or more rows, this is a lot of extra work and is an inefficient process.
The following methodologies may make this process more efficient:
Option 1 is to produce empty or smaller blocks. This simply reduces the size of the Merkle tree and therefore requires fewer hashing operations to generate a different Merkle root hash. The extra nonce can therefore vary in the normal way to produce more Merkle root hashes."
- A few other options to make the process more efficient.
Each option, however, can have an undesirable effect on your operations if not done correctly, which brings me to:
3. Skewed transaction time stamps.
- We are seeing a large # of blocks containing (received) time stamps that are way out out whack. I can think of many reasons this would happen:
- Huge hash increase on local network overloading systems (self inflicted DDoS). Think of a computer processor and system like a highway. Sudden increase of massive amounts of data clogs
things up. Quite simply, if there are any constraints placed upon the call to/from the clock register, there will be time corruption.
- Buggy or flawed/low quality chip design
- Sudden temperature changes
- Environmental issues causing frequency changes
- Power supplies that are not clean/stable
- Packet storms and overloaded network resulting in timing update issues
If current UNIX time is 1530041671 (06/26/2018 @ 7:34pm utc), and system issues result in time being updated or read as say, 1030041671 (one bit off), we see transaction received time set to 12/04/2002 @ 10:41pm UTC
China is supposed putting an end to crypto miners in China. Complete BS obviously.. Seems like they are ramping things up instead.
That is some great analysis and really helps me picture some of what is happening here. Let me ask you though - with all of your facts on mining and such not being my wheelhouse - who can factually prove that Bitcoin (BTC) is directly minting its own new coins? By producing a block reward from mining BTC directly? Are you saying the blocks generated from merge mining are abnormal? I'm saving that Devcoins should not be 1:1 with BTC... |
|
|
|
Facebook Bitcoin Visa Debit Card.   Screw it, I'm in. |
|
|
|
I have read your articles and commend you on your level of insight but was wondering if you ran any of this past any of the i0 coin developers or anyone who worked on its client/codebase recently? Maybe they could chime in with their opinion and add some weight to this? Thanks I hope they do I haven't talked to any directly. However, the Alert Key was just triggered on I0Coin's chainz block explorer. I updated here with photos. Predicted it about 1 hour before it happened! https://medium.com/@danieltreccia/bitcoin-state-reorganization-are-you-prepared-for-june-30-2018-d28cba344ccbI have mentioned it to one person who would have a far greater knowledge of coding than myself and who has actually worked on the client and they don't seem to have any knowledge of there being anything special about i0 coin apart from it being a merge mined coin allowing it this level of hashrate. Just read my entire medium when you have three days free https://medium.com/@danieltreccia/bitcoins-alert-key-triggered-on-i0coin-s-blockchain-ee82e97d4819 |
|
|
|
I have read your articles and commend you on your level of insight but was wondering if you ran any of this past any of the i0 coin developers or anyone who worked on its client/codebase recently? Maybe they could chime in with their opinion and add some weight to this? Thanks I hope they do I haven't talked to any directly. However, the Alert Key was just triggered on I0Coin's chainz block explorer. I updated here with photos. Predicted it about 1 hour before it happened! https://medium.com/@danieltreccia/bitcoin-state-reorganization-are-you-prepared-for-june-30-2018-d28cba344ccb |
|
|
|
(sorry to keep going off-topic on I0coin)
But, my theory is this:
Someone is doing testing or has deployed, or is in the process of deploying, a large amount of ASIC using covert asic BOOST. Reasons being:
1. Sudden large increase of hash power and diff on Bitcoin and Merged-mined BTC coins
2. Empty/small size blocks
- Empty blocks being added to BTC's chain
- Small block sizes
Mining empty blocks and small blocks are clues that covert asic boost is in use. Covert asic boost
"Miners must look for one collision of 4 bytes, which is 32 bits — so this collision is one of 232 hashing attempts. We take the square root this due to the birthday paradox to arrive at a n approximate expected total of 65,536 attempts.
Each attempt may require changing the extra nonce to generate a new Merkle root hash. However, due to the structure of the Merkle tree, this would require even more additional hashing. If we change the extra nonce, a new is hash is required for each row of the Merkle tree. For a large Bitcoin block with perhaps 10 or more rows, this is a lot of extra work and is an inefficient process.
The following methodologies may make this process more efficient:
Option 1 is to produce empty or smaller blocks. This simply reduces the size of the Merkle tree and therefore requires fewer hashing operations to generate a different Merkle root hash. The extra nonce can therefore vary in the normal way to produce more Merkle root hashes."
- A few other options to make the process more efficient.
Each option, however, can have an undesirable effect on your operations if not done correctly, which brings me to:
3. Skewed transaction time stamps.
- We are seeing a large # of blocks containing (received) time stamps that are way out out whack. I can think of many reasons this would happen:
- Huge hash increase on local network overloading systems (self inflicted DDoS). Think of a computer processor and system like a highway. Sudden increase of massive amounts of data clogs
things up. Quite simply, if there are any constraints placed upon the call to/from the clock register, there will be time corruption.
- Buggy or flawed/low quality chip design
- Sudden temperature changes
- Environmental issues causing frequency changes
- Power supplies that are not clean/stable
- Packet storms and overloaded network resulting in timing update issues
If current UNIX time is 1530041671 (06/26/2018 @ 7:34pm utc), and system issues result in time being updated or read as say, 1030041671 (one bit off), we see transaction received time set to 12/04/2002 @ 10:41pm UTC
China is supposed putting an end to crypto miners in China. Complete BS obviously.. Seems like they are ramping things up instead.
That is some great analysis and really helps me picture some of what is happening here. Let me ask you though - with all of your facts on mining and such not being my wheelhouse - who can factually prove that Bitcoin (BTC) is directly minting its own new coins? By producing a block reward from mining BTC directly? What I mean that is it is obvious both I0C and DVC are minting their own coins via their own block reward. We can see that in the raw block data. With BTC we do not see any proof of that, in fact if you have read my Medium posts on Devcoin (DVC) you see that the source of Newly Generated Bitcoins is just a covered up cross-chain transaction where the input is an outbound (vout) block reward of 12.5 DVC. Now read that as much as you need to. It is really hard to word, but the block reward for DVC is supposed to be 50,000 DVC. All one has to do is look in the raw block data to see only 12.5 DVC are awarded in AuxPow to DVC and then that those 12.5 DVC are immediately output to a BTC address. They show up on the BTC ledger at Blockchain.info. How is that not ground breaking? The fact that the DVC vout pubkeyhash meets up with the I0C Op_Hash160 pubkey on the BTC ledger is even further proof that there is certainly a way to reverse these invalid unspent transactions right back to their real main chain of AuxPow - I0C. That's clear as ever in my articles. Combined with your analysis - we see that the ASIC boost proves China is stepping up their mining effort to 51% "BTC". However such an attack can only come by way of them processing BTC transactions, since BTC does not mint its own coins. So then when that attack takes place, the protection mechanism kicks in to reverse all of these invalid "newly generated coins" block rewards to DVC and via AuxPow to I0C. The scenario here is the Devs are protecting Bitcoin by allowing a 51% attack from somewhere only to show a backup plan and 99.99% minted blockchain exists. It won't be able to be 51'd with that amount minted and is very, very secure with the high hash rate I0C DVC + NMC GRP IXC (the original 5 merge mined coins). I believe that will happen very soon. By Q3 - July 1, 2018. So hold onto your belt buckles folks. EDIT: It has to be said, IMO, that I believe Bitmain is going to run this attack as an exercise for Bitcoin's overall health and to prove it is very secure against mining attacks -> this will gain public praise -> mass adoption will follow. |
|
|
|
The network issues 12.5 BTC per block.All this nonsense is non sequitur hyperbole.Even Vlad's notorious friend would agree https://twitter.com/ProfFaustus/status/1011502936772546561.A deliberate sensationalist narrative created out of an insignificant event. The softfork on 528750 block was shitcoin 2x hybrid consensus.Another insignificant bump under the wheels of a freight train. The silence will be deafening once these two copypaste coins i0/IX retract back into tumbleweed town after its pathetic attempt to pump on the back of this urban myth. Just after this fork a character named "BitPico" start a massive ddos and (blocks overload?) to the bcash network... Lot of fud and talkings about Bitmain 51% hspower... I read someone asking how he (BitPico) have such ammount of (block tx?)... I admit to have not enought knowledge to have a clear plot of the situation but something is moving, something of this things are incredibly related with my personal past and last but not least, this is the kind of things that really open your eyes on how much is deep the real world and the stories that everyday humankind is able to make. That's I think sure worth a try ps: IXC and I0C seems to be often negative correlated, so it's easy swap and increase your stack It definitely all seems to intertwine in one way or the other. The Huobi 10 Index HB10 launches July 1. Index coins deserve their credit in forming these types of possibilities for crypto. I0C will have its day. Soon. Has to be. NLX forks this month - expect Zerocoin protocol to make the news. |
|
|
|
|
The funny part is people think its acceptable to have a ledger as sloppy as BTC's:
"Unable to decode output address - (Unspent)"
On every damn block reward. Let alone the source of those "Newly Generated Coins" being withheld.
Matter of days. Truth will shine.
|
|
|
|
|
Show Posts
