[NEW XBY ANN] XTRABYTES - BECAUSE THE BLOCKCHAIN CAN BE BETTER

[enkiamo]

BORZALOM 777

Question 2.

What is the expected timeframe for setting up and auctioning the L1 nodes? Will that be aligned with the level 2 and 3 nodes?

After the STaTiC+PoSign test closed (where we use manual registered STaTiC-s ) then the next test will be the test of STaTiC registration. Each level ( L1,2,3) will be open. The original Level1 STaTiC-s was added to genesis block but all other positions will be available. I don't want wrote deadline of tests but i hope to these tests will be closed this year. This it also depends the teams who help the execute and evaluate of tests. I hope the first teams will be available shortly. If the STaTiC registration tests successed then i will add this code to the system immediatly. And all level of registrations will be available after.

So after a successful STaTiC+PoSign test (which is taking place promptly), all STATIC nodes will be open for registration.  Hopefully, this will all happen before the end of the year.

[1714194577]

1714194577

[CCRevolution]

BORZALOM 777

Question 2.

What is the expected timeframe for setting up and auctioning the L1 nodes? Will that be aligned with the level 2 and 3 nodes?

After the STaTiC+PoSign test closed (where we use manual registered STaTiC-s ) then the next test will be the test of STaTiC registration. Each level ( L1,2,3) will be open. The original Level1 STaTiC-s was added to genesis block but all other positions will be available. I don't want wrote deadline of tests but i hope to these tests will be closed this year. This it also depends the teams who help the execute and evaluate of tests. I hope the first teams will be available shortly. If the STaTiC registration tests successed then i will add this code to the system immediatly. And all level of registrations will be available after.

So after a successful STaTiC+PoSign test (which is taking place promptly), all STATIC nodes will be open for registration.  Hopefully, this will all happen before the end of the year.

Yes, things are moving ahead quite well. If no roadblocks slow us down, maybe we can see this. But, keep in mind he is not setting a date and it could be longer. It will depend on what happens during the tests.

[Seb59]

Hope to have on STATIC for my christmas

[borzalom]

We can see how much Borz pays attention to anything other than programming. As you can see he still has the old blue logo This is how you focus on the tasks at hand... you simply block out everything else because for the most part, it is white noise that does nothing to help him achieve the goals he has in place for XTRABYTES.

Now that he his here, I will send him an updated logo to use.

Logo updated ;-)

[bigboss154]

I'm so used to the blue on borz that now it just seems wrong without it. 

[Sanchoni25]

This year could be best Christmas ever   

[CCRevolution]

This year could be best Christmas ever   

Hey Sanchoni! Good to see you here tonight

[EbenTheva]

This year could be best Christmas ever   

I second it!!

[borzalom]

BORZALOM 777

Question 3.

Has the testnet proven that the technology works and is secure? Are the consensus mechanisms now fully tested?

We have more than just a successed test. We have XFuel where the technology is public available. I hope the XFuel enought secure. 20.000 blocks done and nobody hacked the system. The XFuel contain some finalised parts of the consensus but not each parts. I will be add more and more passed code until we get the final consensus. Of course the final consensus always be changing. The good system opening the door to the changes. I don't want hardcoded consensus like the BTC block size problem or simile other.

[CCRevolution]

BORZALOM 777

Question 4.

How can we validate that XFuel uses the PoSign technology? Is there any technical proof to show how it works?

[Sanchoni25]

This year could be best Christmas ever   

Hey Sanchoni! Good to see you here tonight

Don't worry CCR, you're not going to get rid of me   

[CCRevolution]

This year could be best Christmas ever   

Hey Sanchoni! Good to see you here tonight

Don't worry CCR, you're not going to get rid of me   

Its great to have you as one of our long term XTRABYTES Community Members! We have some nice surprises coming for you and the others soon.

[borzalom]

BORZALOM 777

Question 4.

How can we validate that XFuel uses the PoSign technology? Is there any technical proof to show how it works?

1.) Start XFuel Wallet and enter to debug console

Welcome to the XFuel RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.

2.) Type getinfo

getinfo


{
"version" : 1000001,
"protocolversion" : 10001,
"blocks" : 20012,
"timeoffset" : 0,
"connections" : 3,
"paytxfee" : 0.00000000,
"errors" : ""
}

3.) Get the hash of last block

getblockhash 20012

f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef


4.) Dump the detailed info of this block

getblock f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef


{
"hash" : "f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef",
"confirmations" : 1,
"size" : 282,
"height" : 20012,
"version" : 1,
"merkleroot" : "cab3e8620645adb50a5a7bbe3d156105f64b51983353ee18036228ed0d55ebf5",
"tx" : [
"cab3e8620645adb50a5a7bbe3d156105f64b51983353ee18036228ed0d55ebf5"
],
"time" : 1510086447,
"minerid" : 2,
"signature" : "3045022100a21645344d51435be6d032b44e6d847bfeffbb8c8681fea40a2cf0e5f7c16e4702205 2394414ad868339f434fdb8acfa779d85649d79f51e636036113c010781eaf2",
"previousblockhash" : "10c85a6d2fced7b9c2d111eb87215c2ab06991916ef2c75c0dba992d6a801b79"
}

5.) You see the ID of miner who signed the block and the signature too. The last signer checked and accepted the all previous blocks too

[CCRevolution]

BORZALOM 777

Question 5.

Once PoSign is running, how are blocks created? Will block time remain the same? Like every 30s we’ll “mint” a new block via the static nodes? How do we ensure all transactions are verified by all nodes at the time of minting? We don’t make a new block until all transactions are agreed?

What if we have 2 servers on opposite sides of the world (Say JPY and UK) and it comes time to make a block... UK has no outstanding transactions so it creates it. Before JPY gets the block update it receives a transaction and sends it off to get ok’d by all servers... now we have a fork? How is this handled? Thanks

[dedby]

BORZALOM 777

Question 4.

How can we validate that XFuel uses the PoSign technology? Is there any technical proof to show how it works?

1.) Start XFuel Wallet and enter to debug console

Welcome to the XFuel RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.

2.) Type getinfo

getinfo


{
"version" : 1000001,
"protocolversion" : 10001,
"blocks" : 20012,
"timeoffset" : 0,
"connections" : 3,
"paytxfee" : 0.00000000,
"errors" : ""
}

3.) Get the hash of last block

getblockhash 20012

f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef


4.) Dump the detailed info of this block

getblock f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef


{
"hash" : "f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef",
"confirmations" : 1,
"size" : 282,
"height" : 20012,
"version" : 1,
"merkleroot" : "cab3e8620645adb50a5a7bbe3d156105f64b51983353ee18036228ed0d55ebf5",
"tx" : [
"cab3e8620645adb50a5a7bbe3d156105f64b51983353ee18036228ed0d55ebf5"
],
"time" : 1510086447,
"minerid" : 2,
"signature" : "3045022100a21645344d51435be6d032b44e6d847bfeffbb8c8681fea40a2cf0e5f7c16e4702205 2394414ad868339f434fdb8acfa779d85649d79f51e636036113c010781eaf2",
"previousblockhash" : "10c85a6d2fced7b9c2d111eb87215c2ab06991916ef2c75c0dba992d6a801b79"
}

5.) You see the ID of miner who signed the block and the signature too. The last signer checked and accepted the all previous blocks too

self sign block? wow nem did this at start this bad

[CCRevolution]

BORZALOM 777

Question 4.

How can we validate that XFuel uses the PoSign technology? Is there any technical proof to show how it works?

1.) Start XFuel Wallet and enter to debug console

Welcome to the XFuel RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.

2.) Type getinfo

getinfo


{
"version" : 1000001,
"protocolversion" : 10001,
"blocks" : 20012,
"timeoffset" : 0,
"connections" : 3,
"paytxfee" : 0.00000000,
"errors" : ""
}

3.) Get the hash of last block

getblockhash 20012

f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef


4.) Dump the detailed info of this block

getblock f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef


{
"hash" : "f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef",
"confirmations" : 1,
"size" : 282,
"height" : 20012,
"version" : 1,
"merkleroot" : "cab3e8620645adb50a5a7bbe3d156105f64b51983353ee18036228ed0d55ebf5",
"tx" : [
"cab3e8620645adb50a5a7bbe3d156105f64b51983353ee18036228ed0d55ebf5"
],
"time" : 1510086447,
"minerid" : 2,
"signature" : "3045022100a21645344d51435be6d032b44e6d847bfeffbb8c8681fea40a2cf0e5f7c16e4702205 2394414ad868339f434fdb8acfa779d85649d79f51e636036113c010781eaf2",
"previousblockhash" : "10c85a6d2fced7b9c2d111eb87215c2ab06991916ef2c75c0dba992d6a801b79"
}

5.) You see the ID of miner who signed the block and the signature too. The last signer checked and accepted the all previous blocks too

Very important to also note (for those crypto tech savvy) that these are not BTC clone blocks. These are new blocks and thus proof that we have a new tech at work here in the early stages.

[borzalom]

BORZALOM 777

Question 4.

How can we validate that XFuel uses the PoSign technology? Is there any technical proof to show how it works?

1.) Start XFuel Wallet and enter to debug console

Welcome to the XFuel RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.

2.) Type getinfo

getinfo


{
"version" : 1000001,
"protocolversion" : 10001,
"blocks" : 20012,
"timeoffset" : 0,
"connections" : 3,
"paytxfee" : 0.00000000,
"errors" : ""
}

3.) Get the hash of last block

getblockhash 20012

f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef


4.) Dump the detailed info of this block

getblock f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef


{
"hash" : "f6a45819b5393ccaec23195c012c91c4553b2999a49fb753129d6158dd3858ef",
"confirmations" : 1,
"size" : 282,
"height" : 20012,
"version" : 1,
"merkleroot" : "cab3e8620645adb50a5a7bbe3d156105f64b51983353ee18036228ed0d55ebf5",
"tx" : [
"cab3e8620645adb50a5a7bbe3d156105f64b51983353ee18036228ed0d55ebf5"
],
"time" : 1510086447,
"minerid" : 2,
"signature" : "3045022100a21645344d51435be6d032b44e6d847bfeffbb8c8681fea40a2cf0e5f7c16e4702205 2394414ad868339f434fdb8acfa779d85649d79f51e636036113c010781eaf2",
"previousblockhash" : "10c85a6d2fced7b9c2d111eb87215c2ab06991916ef2c75c0dba992d6a801b79"
}

5.) You see the ID of miner who signed the block and the signature too. The last signer checked and accepted the all previous blocks too

self sign block? wow nem did this at start this bad

Not just self signed. If the miner don't have right to generate and sign the block then all other miners know to try it fake block generation. If you want valid block then the signature only don't enought.

[borzalom]

BORZALOM 777

Question 5.

Once PoSign is running, how are blocks created? Will block time remain the same? Like every 30s we’ll “mint” a new block via the static nodes? How do we ensure all transactions are verified by all nodes at the time of minting? We don’t make a new block until all transactions are agreed?

What if we have 2 servers on opposite sides of the world (Say JPY and UK) and it comes time to make a block... UK has no outstanding transactions so it creates it. Before JPY gets the block update it receives a transaction and sends it off to get ok’d by all servers... now we have a fork? How is this handled? Thanks

Each miner watching lot of different events. Number of transactions and elpassed time of last generated block, who generate the last block etc... Summarize the "value" of this events each block have one "weight". If we have 3 miners and each miner generate block in same time and the generator of last generated block is the #1 miner then the weight of each block is different. The #1 weight is the worster and never be accept this block other miners because the previous block generator is also the #1. The #2 will be the best and the #3 also acceptable if #2 is offline or don't generated block. The block collision is normal event. Each miner and client know what is the "best" block. The block of #2 maybe don't contain all transactions but this is no problem. The next block will be contain the missing transaction. Each block have unique weight therefore never created forks. The chain always contain blocks ordered by weight.

[CCRevolution]

BORZALOM 777

Question 6.

Blockchain generation 3.0 is also about interpolarity, where Blockchains can talk to one another. Are there any future plans for the creation of a module for communication between the ethereum network, and other chains?

[borzalom]

BORZALOM 777

Question 6.

Blockchain generation 3.0 is also about interpolarity, where Blockchains can talk to one another. Are there any future plans for the creation of a module for communication between the ethereum network, and other chains?

The system support this therefore i hope someone will be create interpolarity module. The early stage of system contain the bridge. This bridge connect the old chain and the new chain. These blockchains communicating each other. The future interpolarity module just need extend this function to external blockchains.