ARK - DPoS 🔹 ARK Protokol 🔹 MarketSquare 🔹 IPFS 🔹 Staking on Binance 🔹 - page 653.

cannabanana

hero member

Activity: 518

Merit: 501

Quote from: O_Omaha on October 25, 2016, 03:38:08 PM

Quote from: freemind1 on October 25, 2016, 03:35:19 PM

Quote from: O_Omaha on October 25, 2016, 03:32:14 PM

Quote from: bitseedmike on October 25, 2016, 03:21:20 PM

Yes. We are using a combination of Practical Byzantine Fault Tolerance to pre-approve blocks along the lines of what Asch is doing to prevent forks and forging from uncles to allow delegates to create new blocks in cases where the prior block might still be delayed to decrease latency, decreasing blocktime.

So this will stabilize the core?

Yes @O_Omaha, and allows delegates to forge.

haha you and me are going to get along very well my friend, very well Cheesy

cannabanana

hero member

Activity: 518

Merit: 501

Quote from: MrPresident on October 25, 2016, 03:36:55 PM

WAIT!
If I use my lisk, I'll be using my promised lsk to TD vote-weight.... now what?

those are life's biggest mysteries Grin

O_Omaha

full member

Activity: 159

Merit: 100

Quote from: freemind1 on October 25, 2016, 03:35:19 PM

Quote from: O_Omaha on October 25, 2016, 03:32:14 PM

Quote from: bitseedmike on October 25, 2016, 03:21:20 PM

Yes. We are using a combination of Practical Byzantine Fault Tolerance to pre-approve blocks along the lines of what Asch is doing to prevent forks and forging from uncles to allow delegates to create new blocks in cases where the prior block might still be delayed to decrease latency, decreasing blocktime.

So this will stabilize the core?

Yes @O_Omaha, and allows delegates to forge.

Devasive

full member

Activity: 161

Merit: 100

Quote from: O_Omaha on October 25, 2016, 03:32:14 PM

Quote from: bitseedmike on October 25, 2016, 03:21:20 PM

Yes. We are using a combination of Practical Byzantine Fault Tolerance to pre-approve blocks along the lines of what Asch is doing to prevent forks and forging from uncles to allow delegates to create new blocks in cases where the prior block might still be delayed to decrease latency, decreasing blocktime.

So this will stabilize the core?

Faster block-times as well due to the lower active delegate number of 51.

MrPresident

hero member

Activity: 644

Merit: 500

Think or swim.

WAIT!
I have an itch to spend BTC but there's no ico yet hahaha

cannabanana

hero member

Activity: 518

Merit: 501

Quote from: O_Omaha on October 25, 2016, 03:32:14 PM

Quote from: bitseedmike on October 25, 2016, 03:21:20 PM

Yes. We are using a combination of Practical Byzantine Fault Tolerance to pre-approve blocks along the lines of what Asch is doing to prevent forks and forging from uncles to allow delegates to create new blocks in cases where the prior block might still be delayed to decrease latency, decreasing blocktime.

So this will stabilize the core?

yes. and also with many other things, when you add MORE features to the core you also introduce more points of faults which can be potentially compromised. Our system streamlines our core to make it more secure and fast but also uses other blockchain layers to help handle the issues associated with js.

but Short answer, yes it will fix the problems.

freemind1

legendary

Activity: 1526

Merit: 1014

Quote from: O_Omaha on October 25, 2016, 03:32:14 PM

Quote from: bitseedmike on October 25, 2016, 03:21:20 PM

Yes. We are using a combination of Practical Byzantine Fault Tolerance to pre-approve blocks along the lines of what Asch is doing to prevent forks and forging from uncles to allow delegates to create new blocks in cases where the prior block might still be delayed to decrease latency, decreasing blocktime.

So this will stabilize the core?

Yes @O_Omaha, and allows delegates to forge.

MrPresident

hero member

Activity: 644

Merit: 500

Think or swim.

uuugh, so now I wait. Only 20k lisk in pocket and a gazillion in ICN holding me up as LSK rises haha my luck.

O_Omaha

full member

Activity: 159

Merit: 100

Quote from: bitseedmike on October 25, 2016, 03:21:20 PM

Yes. We are using a combination of Practical Byzantine Fault Tolerance to pre-approve blocks along the lines of what Asch is doing to prevent forks and forging from uncles to allow delegates to create new blocks in cases where the prior block might still be delayed to decrease latency, decreasing blocktime.

So this will stabilize the core?

MrPresident

hero member

Activity: 644

Merit: 500

Think or swim.

Quote from: cannabanana on October 25, 2016, 03:20:15 PM

Quote from: MrPresident on October 25, 2016, 03:16:38 PM

has a forging solution been found? (sorry I had to ask)

yes, we are going to implement pre-approval PBFT blocks. Fixcrypt says that it will do the job right.

Quote from: bitseedmike on October 25, 2016, 03:21:20 PM

Yes. We are using a combination of Practical Byzantine Fault Tolerance to pre-approve blocks along the lines of what Asch is doing to prevent forks and forging from uncles to allow delegates to create new blocks in cases where the prior block might still be delayed to decrease latency, decreasing blocktime.

ooh?... Now I'm impressed all to fuck and back. Wink

cannabanana

hero member

Activity: 518

Merit: 501

Quote from: O_Omaha on October 25, 2016, 03:28:21 PM

Quote from: cannabanana on October 25, 2016, 03:00:13 PM

Quote from: O_Omaha on October 25, 2016, 02:57:12 PM

Quote from: Devasive on October 25, 2016, 02:42:29 PM

Quote from: O_Omaha on October 25, 2016, 02:41:31 PM

I hope this is not another broken down Lisk clone. Will read the white paper and let you know. Tongue

There is much to read! Please share your thoughts after you take it all in.

I like how you are doing the delegate voting. 1 ark is 1 vote. Lisk does it very different. In Lisk the developer has all the voting power. In Ark looks like the developer can vote himself in but if he votes for his buddy, it splits his power over the 2 delegates. Nice change! I like. still reading.

hehe we are well aware of that issue and wanted to correct it for our system as we feel it's a lot more fair. Even when we are done with our token exchange, us individually with our coin split will not have an advantage over the token exchange participants at being able to forge ark

I must say your whitepaper is very impressive! the "smart bridging" feature, if it actually works and I'm assuming here that it does, can be a huge success.

being delegates for Lisk, we've spent a lot of time together discussing in our own private slack what we think will fix the Lisk implementation of DPoS and where it went astray from the objectives of the Crypti.

We decided to go back to square one and develop it fairly with an even more forward thinking way.

O_Omaha

full member

Activity: 159

Merit: 100

Quote from: cannabanana on October 25, 2016, 03:00:13 PM

Quote from: O_Omaha on October 25, 2016, 02:57:12 PM

Quote from: Devasive on October 25, 2016, 02:42:29 PM

Quote from: O_Omaha on October 25, 2016, 02:41:31 PM

I hope this is not another broken down Lisk clone. Will read the white paper and let you know. Tongue

There is much to read! Please share your thoughts after you take it all in.

I like how you are doing the delegate voting. 1 ark is 1 vote. Lisk does it very different. In Lisk the developer has all the voting power. In Ark looks like the developer can vote himself in but if he votes for his buddy, it splits his power over the 2 delegates. Nice change! I like. still reading.

hehe we are well aware of that issue and wanted to correct it for our system as we feel it's a lot more fair. Even when we are done with our token exchange, us individually with our coin split will not have an advantage over the token exchange participants at being able to forge ark

I must say your whitepaper is very impressive! the "smart bridging" feature, if it actually works and I'm assuming here that it does, can be a huge success.

bitseedmike

sr. member

Activity: 432

Merit: 250

Yes. We are using a combination of Practical Byzantine Fault Tolerance to pre-approve blocks along the lines of what Asch is doing to prevent forks and forging from uncles to allow delegates to create new blocks in cases where the prior block might still be delayed to decrease latency, decreasing blocktime.

cannabanana

hero member

Activity: 518

Merit: 501

Quote from: MrPresident on October 25, 2016, 03:16:38 PM

has a forging solution been found? (sorry I had to ask)

yes, we are going to implement pre-approval PBFT blocks. Fixcrypt says that it will do the job right.

MrPresident

hero member

Activity: 644

Merit: 500

Think or swim.

Has a forging solution been found/tested? (sorry, I had to ask)

ArkEcosystem

member

Activity: 70

Merit: 10

Thanks all for the Support! We have really great plans for our organization!

cannabanana

hero member

Activity: 518

Merit: 501

Quote from: O_Omaha on October 25, 2016, 02:57:12 PM

Quote from: Devasive on October 25, 2016, 02:42:29 PM

Quote from: O_Omaha on October 25, 2016, 02:41:31 PM

I hope this is not another broken down Lisk clone. Will read the white paper and let you know. Tongue

There is much to read! Please share your thoughts after you take it all in.

I like how you are doing the delegate voting. 1 ark is 1 vote. Lisk does it very different. In Lisk the developer has all the voting power. In Ark looks like the developer can vote himself in but if he votes for his buddy, it splits his power over the 2 delegates. Nice change! I like. still reading.

hehe we are well aware of that issue and wanted to correct it for our system as we feel it's a lot more fair. Even when we are done with our token exchange, us individually with our coin split will not have an advantage over the token exchange participants at being able to forge ark

O_Omaha

full member

Activity: 159

Merit: 100

Quote from: Devasive on October 25, 2016, 02:42:29 PM

Quote from: O_Omaha on October 25, 2016, 02:41:31 PM

I hope this is not another broken down Lisk clone. Will read the white paper and let you know. Tongue

There is much to read! Please share your thoughts after you take it all in.

I like how you are doing the delegate voting. 1 ark is 1 vote. Lisk does it very different. In Lisk the developer has all the voting power. In Ark looks like the developer can vote himself in but if he votes for his buddy, it splits his power 50/50 over the 2 delegates. Nice change! I like. still reading.

leto.atreides

newbie

Activity: 53

Merit: 0

Quote from: ?? on ??

excellent start guys! good luck

Thank you!

cannabanana

hero member

Activity: 518

Merit: 501

Quote from: O_Omaha on October 25, 2016, 02:41:31 PM

I hope this is not another broken down Lisk clone. Will read the white paper and let you know. Tongue

You also gotta understand who we are. We're basically part of the group that runs a majority of Lisk testnet and mainnet nodes. Not just a copy and paste team.

Topic: ARK - DPoS 🔹 ARK Protokol 🔹 MarketSquare 🔹 IPFS 🔹 Staking on Binance 🔹 - page 653. (Read 781326 times)