Ninjastic
Search content
Sort by
Showing 20 of 126 results by CHIEF56
Post
Topic
Board Announcements (Altcoins)
Re: Network Attack on XVG / VERGE
by
CHIEF56
on 28/06/2018, 14:21:00 UTC
Quote from: ttookk on June 28, 2018, 06:36:29 AM
Well, it's the 1% fee you pay for using the pool, isn't it? I don't see why that would raise any eyebrows. Not *everything* is a conspiracy.

OK, thanks. I see now this is OK to have multiple outputs from the block generation. Only concern would be if the sum of n outputs > block reward + any fees.

Post
Topic
Board Announcements (Altcoins)
Re: Network Attack on XVG / VERGE
by
CHIEF56
on 28/06/2018, 01:33:22 UTC
Quote from: PandoraBounties on June 28, 2018, 01:21:06 AM
Quote from: boxalex on June 24, 2018, 05:05:03 PM
wow, censorship on the official verge topic now (not this topic!):

got these links deleted there, seems truth hurts .....:

Part I: The Verge Hack, Explained, https://blog.theabacus.io/the-verge-hack-explained-7942f63a3017

Part II: Let’s Do the Time Warp Again: The Verge Hack, Part Deux, https://blog.theabacus.io/lets-do-the-time-warp-again-the-verge-hack-part-deux-c6396ab36ecb


WHO has censored it, and why? That would be interesting to know.

Uhh, usually the topic owner
Post
Topic
Board Announcements (Altcoins)
Re: Network Attack on XVG / VERGE
by
CHIEF56
on 28/06/2018, 01:12:54 UTC
Quote from: RzeroD on June 27, 2018, 06:04:13 PM
Quote from: CHIEF56 on June 27, 2018, 04:11:39 PM
Quote from: CHIEF56 on June 27, 2018, 12:06:49 AM
Is this normal activity?

Seems to be causing node to hang for a bit, everything slows down, then blocks will get added sometimes around 6 per minute

Code:
ProcessMessages(61 bytes)
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1239 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
Flushing wallet.dat
Flushed wallet.dat 1ms
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1239 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1286 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1214 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
received getdata for: tx 21babe9b93ed7b0e6283
ProcessMessages(61 bytes)
ProcessMessages(1300 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(498 bytes)
ProcessMessages(61 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
received getdata for: tx fe8dc024c53ed2ee6f8c
ProcessMessages(61 bytes)
ProcessMessages(97 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(55 bytes)
ProcessMessages(205 bytes)
received getdata (5 invsz)
ProcessMessages(498 bytes)
ProcessMessages(55 bytes)
ProcessMessages(745 bytes)
received getdata (20 invsz)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   0 (00:00:00)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530057844000000 (00:04:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530057964000000 (00:06:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530058084000000 (00:08:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530058204000000 (00:10:04)
ProcessMessages(996 bytes)
ProcessMessages(2021 bytes)
received block e4c0d25df4b21f0a730e
SetBestChain: new best=e4c0d25df4b21f0a730e  height=2297220  trust=2297221  date=06/26/18 23:59:04
ProcessBlock: ACCEPTED (blake)
ProcessMessages(61 bytes)
CNode::AskFor block a324987519888f84956b   0 (00:00:00)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
CNode::AskFor block a324987519888f84956b   1530057848000000 (00:04:08)
ProcessMessages(61 bytes)
ProcessMessages(2496 bytes)
received block a324987519888f84956b
Flushing wallet.dat
Flushed wallet.dat 1ms
ProcessBlock: ACCEPTED (x17)
received getdata for: block e4c0d25df4b21f0a730e
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(498 bytes)
ProcessMessages(498 bytes)


For instance:

Wed Jun 27 03:44:43 2018 SetBestChain: new best=f549a96a0fa40086ca75  height=2297595  trust=2297596  date=06/27/18 03:44:23
Wed Jun 27 03:45:03 2018 SetBestChain: new best=10035811aa3f86a04831  height=2297596  trust=2297597  date=06/27/18 03:44:41
Wed Jun 27 03:45:06 2018 SetBestChain: new best=5f0c19c9b9ec08bffd5a  height=2297597  trust=2297598  date=06/27/18 03:40:39
Wed Jun 27 03:45:21 2018 SetBestChain: new best=44d30fba1aa889c95daf  height=2297598  trust=2297599  date=06/27/18 03:40:49
Wed Jun 27 03:45:34 2018 SetBestChain: new best=00000000000005b7216c  height=2297599  trust=2297600  date=06/27/18 03:45:22
Wed Jun 27 03:45:40 2018 SetBestChain: new best=f9029158b50f5b2dddf8  height=2297600  trust=2297601  date=06/27/18 03:45:32
Wed Jun 27 03:45:43 2018 SetBestChain: new best=8ee792488eda35b4d866  height=2297601  trust=2297602  date=06/27/18 03:41:05
Wed Jun 27 03:46:43 2018 SetBestChain: new best=3b3205439b3570f6fa68  height=2297602  trust=2297603  date=06/27/18 03:41:07


In looking at block # 2297601 - hash: dd47e9d87b12fcfd2e603aea7b211202f58d70e457b05721a2100d36ac98d156

How in the world are there 2 OUTPUTS from the coinbase reward?

Transaction hash   dd47e9d87b12fcfd2e603aea7b211202f58d70e457b05721a2100d36ac98d156
Block   2,297,601
Block hash   8ee792488eda35b4d8662a0cc1ebdc3b5807e35536ccdecd0b1e6f18d04a3d28
Total sent   730.00000000 / $16.079
Confirmations   1,346
Coinbase transaction   Yes
 
Inputs
   ~> Block reward and fees (730.00000000/ $16.079)
 
Outputs
 ~> DCh9Px5y2kao6fnFFbCRdZfd9ChzqPrxTw (722.70000000 / $15.918)
 ~> DBY4e5T7UW7o6akHcDoY2MjoFnjQ11yKkm (7.30000000 / $0.161)


This address contains 6112 transactions, all 7.3 xvg, and split off from the coinbase transaction in same method.

Address DBY4e5T7UW7o6akHcDoY2MjoFnjQ11yKkm
Number of transactions: 6,112
Total XVG Received: 162695.04679000






https://bitcointalk.org/index.php?topic=1433925.msg30524678#msg30524678

https://www.nlpool.nl/site/block?id=561




That doesn't explain much and only raises further eyebrows. Thanks anyways
Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 27/06/2018, 22:45:46 UTC
Quote from: realdantreccia on June 26, 2018, 11:46:28 PM
Quote from: CHIEF56 on June 26, 2018, 10:33:13 PM

(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?
Post
Topic
Board Mining (Altcoins)
Re: Bitmain Launches the New Antminer B3 Miner
by
CHIEF56
on 27/06/2018, 20:02:07 UTC
Curious.. Has anyone done some research & opened one of these things up or at least thrown a packet capture on the network?

Are these B3's doing what they are supposed to be doing?
Post
Topic
Board Announcements (Altcoins)
Re: Network Attack on XVG / VERGE
by
CHIEF56
on 27/06/2018, 16:11:39 UTC
Quote from: CHIEF56 on June 27, 2018, 12:06:49 AM
Is this normal activity?

Seems to be causing node to hang for a bit, everything slows down, then blocks will get added sometimes around 6 per minute

Code:
ProcessMessages(61 bytes)
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1239 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
Flushing wallet.dat
Flushed wallet.dat 1ms
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1239 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1286 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1214 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
received getdata for: tx 21babe9b93ed7b0e6283
ProcessMessages(61 bytes)
ProcessMessages(1300 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(498 bytes)
ProcessMessages(61 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
received getdata for: tx fe8dc024c53ed2ee6f8c
ProcessMessages(61 bytes)
ProcessMessages(97 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(55 bytes)
ProcessMessages(205 bytes)
received getdata (5 invsz)
ProcessMessages(498 bytes)
ProcessMessages(55 bytes)
ProcessMessages(745 bytes)
received getdata (20 invsz)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   0 (00:00:00)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530057844000000 (00:04:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530057964000000 (00:06:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530058084000000 (00:08:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530058204000000 (00:10:04)
ProcessMessages(996 bytes)
ProcessMessages(2021 bytes)
received block e4c0d25df4b21f0a730e
SetBestChain: new best=e4c0d25df4b21f0a730e  height=2297220  trust=2297221  date=06/26/18 23:59:04
ProcessBlock: ACCEPTED (blake)
ProcessMessages(61 bytes)
CNode::AskFor block a324987519888f84956b   0 (00:00:00)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
CNode::AskFor block a324987519888f84956b   1530057848000000 (00:04:08)
ProcessMessages(61 bytes)
ProcessMessages(2496 bytes)
received block a324987519888f84956b
Flushing wallet.dat
Flushed wallet.dat 1ms
ProcessBlock: ACCEPTED (x17)
received getdata for: block e4c0d25df4b21f0a730e
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(498 bytes)
ProcessMessages(498 bytes)


For instance:

Wed Jun 27 03:44:43 2018 SetBestChain: new best=f549a96a0fa40086ca75  height=2297595  trust=2297596  date=06/27/18 03:44:23
Wed Jun 27 03:45:03 2018 SetBestChain: new best=10035811aa3f86a04831  height=2297596  trust=2297597  date=06/27/18 03:44:41
Wed Jun 27 03:45:06 2018 SetBestChain: new best=5f0c19c9b9ec08bffd5a  height=2297597  trust=2297598  date=06/27/18 03:40:39
Wed Jun 27 03:45:21 2018 SetBestChain: new best=44d30fba1aa889c95daf  height=2297598  trust=2297599  date=06/27/18 03:40:49
Wed Jun 27 03:45:34 2018 SetBestChain: new best=00000000000005b7216c  height=2297599  trust=2297600  date=06/27/18 03:45:22
Wed Jun 27 03:45:40 2018 SetBestChain: new best=f9029158b50f5b2dddf8  height=2297600  trust=2297601  date=06/27/18 03:45:32
Wed Jun 27 03:45:43 2018 SetBestChain: new best=8ee792488eda35b4d866  height=2297601  trust=2297602  date=06/27/18 03:41:05
Wed Jun 27 03:46:43 2018 SetBestChain: new best=3b3205439b3570f6fa68  height=2297602  trust=2297603  date=06/27/18 03:41:07


In looking at block # 2297601 - hash: dd47e9d87b12fcfd2e603aea7b211202f58d70e457b05721a2100d36ac98d156

How in the world are there 2 OUTPUTS from the coinbase reward?

Transaction hash   dd47e9d87b12fcfd2e603aea7b211202f58d70e457b05721a2100d36ac98d156
Block   2,297,601
Block hash   8ee792488eda35b4d8662a0cc1ebdc3b5807e35536ccdecd0b1e6f18d04a3d28
Total sent   730.00000000 / $16.079
Confirmations   1,346
Coinbase transaction   Yes
 
Inputs
   ~> Block reward and fees (730.00000000/ $16.079)
 
Outputs
 ~> DCh9Px5y2kao6fnFFbCRdZfd9ChzqPrxTw (722.70000000 / $15.918)
 ~> DBY4e5T7UW7o6akHcDoY2MjoFnjQ11yKkm (7.30000000 / $0.161)


This address contains 6112 transactions, all 7.3 xvg, and split off from the coinbase transaction in same method.

Address DBY4e5T7UW7o6akHcDoY2MjoFnjQ11yKkm
Number of transactions: 6,112
Total XVG Received: 162695.04679000




Post
Topic
Board Announcements (Altcoins)
Re: Network Attack on XVG / VERGE
by
CHIEF56
on 27/06/2018, 00:06:49 UTC
Is this normal activity?

Seems to be causing node to hang for a bit, everything slows down, then blocks will get added sometimes around 6 per minute

Code:
ProcessMessages(61 bytes)
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1239 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
Flushing wallet.dat
Flushed wallet.dat 1ms
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1239 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1286 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1214 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
received getdata for: tx 21babe9b93ed7b0e6283
ProcessMessages(61 bytes)
ProcessMessages(1300 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(97 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1178 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(498 bytes)
ProcessMessages(61 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
received getdata for: tx fe8dc024c53ed2ee6f8c
ProcessMessages(61 bytes)
ProcessMessages(97 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(61 bytes)
ProcessMessages(133 bytes)
ProcessMessages(55 bytes)
ProcessMessages(205 bytes)
received getdata (5 invsz)
ProcessMessages(498 bytes)
ProcessMessages(55 bytes)
ProcessMessages(745 bytes)
received getdata (20 invsz)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   0 (00:00:00)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530057844000000 (00:04:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530057964000000 (00:06:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530058084000000 (00:08:04)
ProcessMessages(61 bytes)
CNode::AskFor block e4c0d25df4b21f0a730e   1530058204000000 (00:10:04)
ProcessMessages(996 bytes)
ProcessMessages(2021 bytes)
received block e4c0d25df4b21f0a730e
SetBestChain: new best=e4c0d25df4b21f0a730e  height=2297220  trust=2297221  date=06/26/18 23:59:04
ProcessBlock: ACCEPTED (blake)
ProcessMessages(61 bytes)
CNode::AskFor block a324987519888f84956b   0 (00:00:00)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
ProcessMessages(61 bytes)
CNode::AskFor block a324987519888f84956b   1530057848000000 (00:04:08)
ProcessMessages(61 bytes)
ProcessMessages(2496 bytes)
received block a324987519888f84956b
Flushing wallet.dat
Flushed wallet.dat 1ms
ProcessBlock: ACCEPTED (x17)
received getdata for: block e4c0d25df4b21f0a730e
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(1117 bytes)
getblocks -1 to 00000000000000000000 limit 500
ProcessMessages(498 bytes)
ProcessMessages(498 bytes)
ProcessMessages(498 bytes)
Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 26/06/2018, 22:33:13 UTC
Quote from: CHIEF56 on June 25, 2018, 11:45:59 PM
Quote from: CHIEF56 on June 24, 2018, 03:56:48 PM
Quote from: realdantreccia on June 24, 2018, 03:37:35 PM
Quote from: CHIEF56 on June 24, 2018, 04:04:15 AM
Quote from: realdantreccia on June 23, 2018, 11:31:08 PM
Quote from: CHIEF56 on June 23, 2018, 11:26:56 PM
Quote from: CHIEF56 on June 23, 2018, 10:21:33 PM
Quote from: realdantreccia on June 23, 2018, 12:13:56 AM
Quote from: CHIEF56 on June 23, 2018, 12:13:20 AM
Quote from: realdantreccia on June 22, 2018, 11:52:50 PM
I knew something happened at the end of 2017 to make the Bitcoin we have seen in 2018 "different" ... Never seen an empty block like this...

https://blockchain.info/block/0000000000000000004b27f9ee7ba33d6f048f684aaeb0eea4befd80f1701126

Ahh, that's an odd one.

Transaction fee of -12.5 BTC  Smiley

State reorganization underway for BTC.  F2Pool is the mining pool submitting blocks from the early 2000's.

Pardon, but what is block version 0x3FFFE000

?

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b?format=json



Ahh.. BIP-9 version bits set by F2 pool signaling set up of soft forks, I guess. So much reading to do and so far behind  Embarrassed

https://bitcointicker.co/block/528898  -  0x3fffe000

https://bitcointicker.co/block/528908  -  0x2000e000

https://bitcointicker.co/block/528916  -  0x3fffffff

 

If only I knew coding. Haha.

Code:
https://bitcointicker.co/block/528898  -  F2Pool  -  0x3fffe000
https://bitcointicker.co/block/528908  -  F2Pool  -  0x2000e000  <~
https://bitcointicker.co/block/528916  -  F2Pool  -  0x3fffffff
https://bitcointicker.co/block/528932  -  CKpool  -  0x2000e000  <~

What's your take on the version?

Which part of it? What do the values translate into exactly, you mean? I'd have to research more into them.

What does it mean overall? The miners are signaling soft forks. I believe, once 97% ? of miners are in agreement, it happens. Correct me if I am wrong, but by F2Pool + and then CKpool setting the same bits, that equals more than 1% of the miners agree on 0x2000e000




I should have read more earlier, but:

Actually, the use and change we are seeing here is indicative of the fact that miners of those pools are solving blocks using version-rolling ASICBOOST . . . Either (1) overtly (2) covertly, or both.

BIP661 reserved a range of values in the Version field for this purpose, or other functions: https://github.com/bitcoin/bips/pull/661/files

And just recent: https://bitcointicker.co/block/529235  -  BTC.top

Overt AsicBoost

Instead of changing the extra nonce, a miner using AsicBoost alters the 4-byte version field in the block header (top left of the image). This implies that chunk 2 remains unchanged for multiple hashing attempts and work is therefore saved. If this methodology is used, changes in the version bits are visible to everyone, which makes this AsicBoost methodology easily detectable.
(more: https://blog.bitmex.com/an-overview-of-the-covert-asicboost-allegation-2/)

Somewhere in the following links, explanations are found for the large number of empty blocks and skewed timestamps.. no more time for me to look at the moment:


https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html

https://blog.bitmex.com/graphical-illustration-of-a-bitcoin-block/

https://blog.bitmex.com/wp-content/uploads/2017/09/AsicBoostWhitepaperrev5.pdf

https://blog.bitmex.com/an-overview-of-the-covert-asicboost-allegation-2/

https://blog.bitmex.com/empty-block-data-by-mining-pool/

https://blog.bitmex.com/wp-content/uploads/2017/09/AsicBoostWhitepaperrev5.pdf



(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.

Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 26/06/2018, 16:05:51 UTC
What event happened here? Code change?


Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 26/06/2018, 05:15:20 UTC
I0coin hash rate is 4000 PH/s ? dafuk?
Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 26/06/2018, 02:11:49 UTC
Quote from: realdantreccia on June 26, 2018, 01:42:34 AM
Everyone has a reason for everything - but this is not a normal sequence of events.  There is no possible way any developer could say "all is going according to plan"...

Unless a state reorganization was intended for the only 2 Bitcoin "copies" when they were 99.99% minted and quantum computing/AI was clearly ready to make it all go down.

That's just how I see it though.

These are interesting times we are living in. And for more reasons than just 1.
Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 25/06/2018, 23:45:59 UTC
Quote from: CHIEF56 on June 24, 2018, 03:56:48 PM
Quote from: realdantreccia on June 24, 2018, 03:37:35 PM
Quote from: CHIEF56 on June 24, 2018, 04:04:15 AM
Quote from: realdantreccia on June 23, 2018, 11:31:08 PM
Quote from: CHIEF56 on June 23, 2018, 11:26:56 PM
Quote from: CHIEF56 on June 23, 2018, 10:21:33 PM
Quote from: realdantreccia on June 23, 2018, 12:13:56 AM
Quote from: CHIEF56 on June 23, 2018, 12:13:20 AM
Quote from: realdantreccia on June 22, 2018, 11:52:50 PM
I knew something happened at the end of 2017 to make the Bitcoin we have seen in 2018 "different" ... Never seen an empty block like this...

https://blockchain.info/block/0000000000000000004b27f9ee7ba33d6f048f684aaeb0eea4befd80f1701126

Ahh, that's an odd one.

Transaction fee of -12.5 BTC  Smiley

State reorganization underway for BTC.  F2Pool is the mining pool submitting blocks from the early 2000's.

Pardon, but what is block version 0x3FFFE000

?

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b?format=json



Ahh.. BIP-9 version bits set by F2 pool signaling set up of soft forks, I guess. So much reading to do and so far behind  Embarrassed

https://bitcointicker.co/block/528898  -  0x3fffe000

https://bitcointicker.co/block/528908  -  0x2000e000

https://bitcointicker.co/block/528916  -  0x3fffffff

 

If only I knew coding. Haha.

Code:
https://bitcointicker.co/block/528898  -  F2Pool  -  0x3fffe000
https://bitcointicker.co/block/528908  -  F2Pool  -  0x2000e000  <~
https://bitcointicker.co/block/528916  -  F2Pool  -  0x3fffffff
https://bitcointicker.co/block/528932  -  CKpool  -  0x2000e000  <~

What's your take on the version?

Which part of it? What do the values translate into exactly, you mean? I'd have to research more into them.

What does it mean overall? The miners are signaling soft forks. I believe, once 97% ? of miners are in agreement, it happens. Correct me if I am wrong, but by F2Pool + and then CKpool setting the same bits, that equals more than 1% of the miners agree on 0x2000e000




I should have read more earlier, but:

Actually, the use and change we are seeing here is indicative of the fact that miners of those pools are solving blocks using version-rolling ASICBOOST . . . Either (1) overtly (2) covertly, or both.

BIP661 reserved a range of values in the Version field for this purpose, or other functions: https://github.com/bitcoin/bips/pull/661/files

And just recent: https://bitcointicker.co/block/529235  -  BTC.top

Overt AsicBoost

Instead of changing the extra nonce, a miner using AsicBoost alters the 4-byte version field in the block header (top left of the image). This implies that chunk 2 remains unchanged for multiple hashing attempts and work is therefore saved. If this methodology is used, changes in the version bits are visible to everyone, which makes this AsicBoost methodology easily detectable.
(more: https://blog.bitmex.com/an-overview-of-the-covert-asicboost-allegation-2/)

Somewhere in the following links, explanations are found for the large number of empty blocks and skewed timestamps.. no more time for me to look at the moment:


https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html

https://blog.bitmex.com/graphical-illustration-of-a-bitcoin-block/

https://blog.bitmex.com/wp-content/uploads/2017/09/AsicBoostWhitepaperrev5.pdf

https://blog.bitmex.com/an-overview-of-the-covert-asicboost-allegation-2/

https://blog.bitmex.com/empty-block-data-by-mining-pool/

https://blog.bitmex.com/wp-content/uploads/2017/09/AsicBoostWhitepaperrev5.pdf


Post
Topic
Board Announcements (Altcoins)
Re: Network Attack on XVG / VERGE
by
CHIEF56
on 24/06/2018, 18:02:22 UTC
Quote from: boxalex on June 24, 2018, 05:18:48 PM
no, this one is on this topic, on the official verge topic i posted the links above as a response to:


I see. Not surprising.
Post
Topic
Board Announcements (Altcoins)
Re: Network Attack on XVG / VERGE
by
CHIEF56
on 24/06/2018, 17:13:00 UTC
Quote from: boxalex on June 24, 2018, 05:05:03 PM
wow, censorship on the verge topic now:

got these links deleted there, seems truth hurts .....:

Part I: The Verge Hack, Explained, https://blog.theabacus.io/the-verge-hack-explained-7942f63a3017

Part II: Let’s Do the Time Warp Again: The Verge Hack, Part Deux, https://blog.theabacus.io/lets-do-the-time-warp-again-the-verge-hack-part-deux-c6396ab36ecb



I saw you post earlier. This one? https://bitcointalk.org/index.php?topic=3256693.msg40793167#msg40793167
Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 24/06/2018, 15:56:48 UTC
Quote from: realdantreccia on June 24, 2018, 03:37:35 PM
Quote from: CHIEF56 on June 24, 2018, 04:04:15 AM
Quote from: realdantreccia on June 23, 2018, 11:31:08 PM
Quote from: CHIEF56 on June 23, 2018, 11:26:56 PM
Quote from: CHIEF56 on June 23, 2018, 10:21:33 PM
Quote from: realdantreccia on June 23, 2018, 12:13:56 AM
Quote from: CHIEF56 on June 23, 2018, 12:13:20 AM
Quote from: realdantreccia on June 22, 2018, 11:52:50 PM
I knew something happened at the end of 2017 to make the Bitcoin we have seen in 2018 "different" ... Never seen an empty block like this...

https://blockchain.info/block/0000000000000000004b27f9ee7ba33d6f048f684aaeb0eea4befd80f1701126

Ahh, that's an odd one.

Transaction fee of -12.5 BTC  Smiley

State reorganization underway for BTC.  F2Pool is the mining pool submitting blocks from the early 2000's.

Pardon, but what is block version 0x3FFFE000

?

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b?format=json



Ahh.. BIP-9 version bits set by F2 pool signaling set up of soft forks, I guess. So much reading to do and so far behind  Embarrassed

https://bitcointicker.co/block/528898  -  0x3fffe000

https://bitcointicker.co/block/528908  -  0x2000e000

https://bitcointicker.co/block/528916  -  0x3fffffff

 

If only I knew coding. Haha.

Code:
https://bitcointicker.co/block/528898  -  F2Pool  -  0x3fffe000
https://bitcointicker.co/block/528908  -  F2Pool  -  0x2000e000  <~
https://bitcointicker.co/block/528916  -  F2Pool  -  0x3fffffff
https://bitcointicker.co/block/528932  -  CKpool  -  0x2000e000  <~

What's your take on the version?

Which part of it? What do the values translate into exactly, you mean? I'd have to research more into them.

What does it mean overall? The miners are signaling soft forks. I believe, once 97% ? of miners are in agreement, it happens. Correct me if I am wrong, but by F2Pool + and then CKpool setting the same bits, that equals more than 1% of the miners agree on 0x2000e000


Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 24/06/2018, 04:04:15 UTC
Quote from: realdantreccia on June 23, 2018, 11:31:08 PM
Quote from: CHIEF56 on June 23, 2018, 11:26:56 PM
Quote from: CHIEF56 on June 23, 2018, 10:21:33 PM
Quote from: realdantreccia on June 23, 2018, 12:13:56 AM
Quote from: CHIEF56 on June 23, 2018, 12:13:20 AM
Quote from: realdantreccia on June 22, 2018, 11:52:50 PM
I knew something happened at the end of 2017 to make the Bitcoin we have seen in 2018 "different" ... Never seen an empty block like this...

https://blockchain.info/block/0000000000000000004b27f9ee7ba33d6f048f684aaeb0eea4befd80f1701126

Ahh, that's an odd one.

Transaction fee of -12.5 BTC  Smiley

State reorganization underway for BTC.  F2Pool is the mining pool submitting blocks from the early 2000's.

Pardon, but what is block version 0x3FFFE000

?

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b?format=json



Ahh.. BIP-9 version bits set by F2 pool signaling set up of soft forks, I guess. So much reading to do and so far behind  Embarrassed

https://bitcointicker.co/block/528898  -  0x3fffe000

https://bitcointicker.co/block/528908  -  0x2000e000

https://bitcointicker.co/block/528916  -  0x3fffffff

 

If only I knew coding. Haha.

Code:
https://bitcointicker.co/block/528898  -  F2Pool  -  0x3fffe000
https://bitcointicker.co/block/528908  -  F2Pool  -  0x2000e000  <~
https://bitcointicker.co/block/528916  -  F2Pool  -  0x3fffffff
https://bitcointicker.co/block/528932  -  CKpool  -  0x2000e000  <~
Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 23/06/2018, 23:26:56 UTC
Quote from: CHIEF56 on June 23, 2018, 10:21:33 PM
Quote from: realdantreccia on June 23, 2018, 12:13:56 AM
Quote from: CHIEF56 on June 23, 2018, 12:13:20 AM
Quote from: realdantreccia on June 22, 2018, 11:52:50 PM
I knew something happened at the end of 2017 to make the Bitcoin we have seen in 2018 "different" ... Never seen an empty block like this...

https://blockchain.info/block/0000000000000000004b27f9ee7ba33d6f048f684aaeb0eea4befd80f1701126

Ahh, that's an odd one.

Transaction fee of -12.5 BTC  Smiley

State reorganization underway for BTC.  F2Pool is the mining pool submitting blocks from the early 2000's.

Pardon, but what is block version 0x3FFFE000

?

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b?format=json



Ahh.. BIP-9 version bits set by F2 pool signaling set up of soft forks, I guess. So much reading to do and so far behind  Embarrassed

https://bitcointicker.co/block/528898  -  0x3fffe000

https://bitcointicker.co/block/528908  -  0x2000e000

https://bitcointicker.co/block/528916  -  0x3fffffff

 
Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 23/06/2018, 22:21:33 UTC
Quote from: realdantreccia on June 23, 2018, 12:13:56 AM
Quote from: CHIEF56 on June 23, 2018, 12:13:20 AM
Quote from: realdantreccia on June 22, 2018, 11:52:50 PM
I knew something happened at the end of 2017 to make the Bitcoin we have seen in 2018 "different" ... Never seen an empty block like this...

https://blockchain.info/block/0000000000000000004b27f9ee7ba33d6f048f684aaeb0eea4befd80f1701126

Ahh, that's an odd one.

Transaction fee of -12.5 BTC  Smiley

State reorganization underway for BTC.  F2Pool is the mining pool submitting blocks from the early 2000's.

Pardon, but what is block version 0x3FFFE000

?

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b

https://blockchain.info/block/0000000000000000001955aec280e6803720da428144b9bcd8adaea039a83f0b?format=json

Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 23/06/2018, 18:41:42 UTC
Quote from: Vlad2Vlad on June 23, 2018, 05:52:51 PM
Quote from: CHIEF56 on June 23, 2018, 05:37:00 PM

Anyways... I'm pretty sure I know or suspect what is going on, but don't really want to discuss attack details in public ;/

Please do.  For the sake of honesty and the benefit of others.  Smiley

Maybe.. Though I don't know if I am convinced enough from looking at the "state of security" of crypto development currently that doing so would prove beneficial. Seems no one gives a shit. Unless I am missing some good discussions that are out there..
Post
Topic
Board Announcements (Altcoins)
Re: [I0C] I0coin - The Best Choice In Digital Currency
by
CHIEF56
on 23/06/2018, 17:37:00 UTC
Quote from: realdantreccia on June 23, 2018, 05:10:06 PM
Quote from: CHIEF56 on June 23, 2018, 12:32:35 AM
Quote from: realdantreccia on June 23, 2018, 12:13:56 AM
Quote from: CHIEF56 on June 23, 2018, 12:13:20 AM
Quote from: realdantreccia on June 22, 2018, 11:52:50 PM
I knew something happened at the end of 2017 to make the Bitcoin we have seen in 2018 "different" ... Never seen an empty block like this...

https://blockchain.info/block/0000000000000000004b27f9ee7ba33d6f048f684aaeb0eea4befd80f1701126

Ahh, that's an odd one.

Transaction fee of -12.5 BTC  Smiley

State reorganization underway for BTC.  F2Pool is the mining pool submitting blocks from the early 2000's.

Yeah.. 1999 now..




 Grin

Anyways... I'm pretty sure I know or suspect what is going on, but don't really want to discuss attack details in public ;/