|
BlackMarket
Sr. Member
Offline
Activity: 322
Merit: 250
Super Smash Bros. Ultimate Available Now!
|
|
November 11, 2014, 06:58:54 PM |
|
|
|
|
|
dodgecharger
|
|
November 11, 2014, 07:01:01 PM |
|
ok, maybe the problem is with Bter thank you
|
|
|
|
|
GreenDude
|
|
November 11, 2014, 07:26:17 PM |
|
I like this, I keep forging. And there is no inflation eating coin value if price rise.
|
|
|
|
|
3x2
Legendary
Offline
Activity: 1526
Merit: 1004
|
|
November 11, 2014, 09:00:11 PM |
|
Volume is quite good and someone just bought 2btc worth NODE, 100sathosis soon
|
|
|
|
bitwhizz
Legendary
Offline
Activity: 910
Merit: 1000
|
|
November 11, 2014, 10:54:21 PM |
|
How long until nodepay is out?
|
|
|
|
u5sos
Member
Offline
Activity: 108
Merit: 10
|
|
November 11, 2014, 10:58:37 PM |
|
How long until nodepay is out?
Devs said that will be in February
|
|
|
|
Hueristic
Legendary
Offline
Activity: 3962
Merit: 5384
Doomed to see the future and unable to prevent it
|
|
November 11, 2014, 11:36:56 PM |
|
Wallet stuck. Tried twice. Loading ... Please wait! Download blocks start. Download block at height: 3382
|
“Bad men need nothing more to compass their ends, than that good men should look on and do nothing.”
|
|
|
GreenDude
|
|
November 11, 2014, 11:50:46 PM |
|
Wallet stuck. Tried twice. Loading ... Please wait! Download blocks start. Download block at height: 3382 Im on block 3387
|
|
|
|
kripto
Member
Offline
Activity: 70
Merit: 10
|
|
November 11, 2014, 11:53:03 PM |
|
Wallet stuck. Tried twice. Loading ... Please wait! Download blocks start. Download block at height: 3382 Im on block 3387 so am i
|
|
|
|
jwilford
|
|
November 12, 2014, 12:01:06 AM |
|
Does anyone know how the POA works. The white paper states that a node broadcasts when it joins the network. Theoretically this could be forced by broadcasting when a request for the blockchain is made. It also says "the network will be scouting the most active node by nodeheight" at that point you could determine if a node was still logged in by seeing if it responds to your inquiry. In my assumption about how you could force a node to broadcast when it joins the network you could also determine when it leaves and rejoins as long as one block had been generated between it leaving and rejoining because it would require an update. So what prevents an attacker from building a bot programmed to log in to one random node every second and keeping a log. While simultaneously another bot stays logged in to a node and starts feeding the latest blocks to the first bot and waits for the network to start calling up the first node that bot 1 logged in to or until a node with that same nodeheight forges. At this point bot 1 would then go back to the second node that it logged in to and wait for it to be called up. A new request for the blockchain would not be necessary since it is being fed the block chain by the second bot. It would then wait for that node to be called up to forge (It can be assumed that since it's height would only be one less than the first node that it would not take long for the new node to be called up.) forge a block then send the transaction fee to the attackers node. It could then sequentially go through each of the nodes it logged in to and repeat this process. In this scenario it would not be advantageous or practical for the bot to try and compromise the chain only to siphon the fees. I guess my larger question in presenting this scenario is what keeps a node honest about it's nodeheight? Right now it is the 500k min that prices someone out of having too many nodes that are eligible to forge but we're all aware that, that nodecoin min is not sustainable for widespread adoption. So this fee would have to be lowered. Once it is this discourages new comers from gaming the system by pricing them out but what discourages the whales from gaming the system in this way. If there is a periodic way to verify activity which would force someone to actually be logged in at that point the price of hardware itself might price people out but if there is not this may show to be problematic. I do not post this to spread FUD, I haven't dumped my nodecoin and don't plan on it. If there is a simple answer to these questions please help me out but I would much rather reveal a flaw in the system now while it is relatively easy to fix than find out later when the effects will be much more detrimental to the system.
|
|
|
|
Hueristic
Legendary
Offline
Activity: 3962
Merit: 5384
Doomed to see the future and unable to prevent it
|
|
November 12, 2014, 12:06:37 AM |
|
Wallet stuck. Tried twice. Loading ... Please wait! Download blocks start. Download block at height: 3382 Im on block 3387 3rd times a charm. worked this time without getting stuck.
|
“Bad men need nothing more to compass their ends, than that good men should look on and do nothing.”
|
|
|
GreenDude
|
|
November 12, 2014, 12:15:06 AM |
|
Does anyone know how the POA works. The white paper states that a node broadcasts when it joins the network. Theoretically this could be forced by broadcasting when a request for the blockchain is made. It also says "the network will be scouting the most active node by nodeheight" at that point you could determine if a node was still logged in by seeing if it responds to your inquiry. In my assumption about how you could force a node to broadcast when it joins the network you could also determine when it leaves and rejoins as long as one block had been generated between it leaving and rejoining because it would require an update. So what prevents an attacker from building a bot programmed to log in to one random node every second and keeping a log. While simultaneously another bot stays logged in to a node and starts feeding the latest blocks to the first bot and waits for the network to start calling up the first node that bot 1 logged in to or until a node with that same nodeheight forges. At this point bot 1 would then go back to the second node that it logged in to and wait for it to be called up. A new request for the blockchain would not be necessary since it is being fed the block chain by the second bot. It would then wait for that node to be called up to forge (It can be assumed that since it's height would only be one less than the first node that it would not take long for the new node to be called up.) forge a block then send the transaction fee to the attackers node. It could then sequentially go through each of the nodes it logged in to and repeat this process. In this scenario it would not be advantageous or practical for the bot to try and compromise the chain only to siphon the fees. I guess my larger question in presenting this scenario is what keeps a node honest about it's nodeheight? Right now it is the 500k min that prices someone out of having too many nodes that are eligible to forge but we're all aware that, that nodecoin min is not sustainable for widespread adoption. So this fee would have to be lowered. Once it is this discourages new comers from gaming the system by pricing them out but what discourages the whales from gaming the system in this way. If there is a periodic way to verify activity which would force someone to actually be logged in at that point the price of hardware itself might price people out but if there is not this may show to be problematic. I do not post this to spread FUD, I haven't dumped my nodecoin and don't plan on it. If there is a simple answer to these questions please help me out but I would much rather reveal a flaw in the system now while it is relatively easy to fix than find out later when the effects will be much more detrimental to the system. I think that is too much work for probably forging 0.001 node and someone doing that would be spending a lot more than what could possibly win. Transaction fees will be lowered every 3 months and with 500k rule u totally prevent someone could have some benefit from doing that. The 500k rule at this moment is ok because price is really low.. but as the price goes up that rule could ofc be changed.
|
|
|
|
GreenDude
|
|
November 12, 2014, 12:18:46 AM |
|
Anyway u could go back and find this discussion already made by patmast3r and silkk and another guys already if u have doubts.
|
|
|
|
jwilford
|
|
November 12, 2014, 12:27:22 AM |
|
Does anyone know how the POA works. The white paper states that a node broadcasts when it joins the network. Theoretically this could be forced by broadcasting when a request for the blockchain is made. It also says "the network will be scouting the most active node by nodeheight" at that point you could determine if a node was still logged in by seeing if it responds to your inquiry. In my assumption about how you could force a node to broadcast when it joins the network you could also determine when it leaves and rejoins as long as one block had been generated between it leaving and rejoining because it would require an update. So what prevents an attacker from building a bot programmed to log in to one random node every second and keeping a log. While simultaneously another bot stays logged in to a node and starts feeding the latest blocks to the first bot and waits for the network to start calling up the first node that bot 1 logged in to or until a node with that same nodeheight forges. At this point bot 1 would then go back to the second node that it logged in to and wait for it to be called up. A new request for the blockchain would not be necessary since it is being fed the block chain by the second bot. It would then wait for that node to be called up to forge (It can be assumed that since it's height would only be one less than the first node that it would not take long for the new node to be called up.) forge a block then send the transaction fee to the attackers node. It could then sequentially go through each of the nodes it logged in to and repeat this process. In this scenario it would not be advantageous or practical for the bot to try and compromise the chain only to siphon the fees. I guess my larger question in presenting this scenario is what keeps a node honest about it's nodeheight? Right now it is the 500k min that prices someone out of having too many nodes that are eligible to forge but we're all aware that, that nodecoin min is not sustainable for widespread adoption. So this fee would have to be lowered. Once it is this discourages new comers from gaming the system by pricing them out but what discourages the whales from gaming the system in this way. If there is a periodic way to verify activity which would force someone to actually be logged in at that point the price of hardware itself might price people out but if there is not this may show to be problematic. I do not post this to spread FUD, I haven't dumped my nodecoin and don't plan on it. If there is a simple answer to these questions please help me out but I would much rather reveal a flaw in the system now while it is relatively easy to fix than find out later when the effects will be much more detrimental to the system. I think that is too much fantasy for probably forging 0.001 node and someone doing that would be spending a lot more than what could possibly win. Transaction fees will be lowered every 3 months and with 500k rule u totally prevent someone could have some benefit from doing that. The 500k rule at this moment is ok because price is really low.. but as the price goes up that rule could ofc be changed. Well I agree with that assessment now but if we ever hit BTC levels the stakes will be MUCH higher. Also I have been continuously logged in with 805,314.53233 nodecoin for 10hrs and haven't forged a block yet (I forged one early this morning but not since) yet the last 27 blocks have been forged by only 7 addresses. Looking at only the top one they have not had a transaction for 4 hours so sent coin should not factor. Last 27 transactions. 8972433069625705159 11993447274130959091 8972433069625705159 3287632914591020592 8972433069625705159 9365254712366913018 8972433069625705159 11363936448759590364 8972433069625705159 6237362358633347087 11363936448759590364 8972433069625705159 6237362358633347087 11363936448759590364 2959762862535928566 6237362358633347087 11363936448759590364 2959762862535928566 6237362358633347087 11363936448759590364 8972433069625705159 11363936448759590364 8972433069625705159 11363936448759590364 6237362358633347087 With duplicates removed 8972433069625705159 11993447274130959091 3287632914591020592 9365254712366913018 11363936448759590364 6237362358633347087 2959762862535928566 My account 8669748491995928868 Have we gone back to random forging or something? Sorry I know I sound like a naysayer today, I'm just trying to understand everything.
|
|
|
|
jwilford
|
|
November 12, 2014, 12:29:13 AM |
|
Anyway u could go back and find this discussion already made by patmast3r and silkk and another guys already if u have doubts.
I will check it out. Thanks.
|
|
|
|
rramires
|
|
November 12, 2014, 12:33:07 AM |
|
This coin was made from scratch inspired in NXT or uses their code changed? I saw that folder where are the data: C:\nxtl\db
|
|
|
|
gentlemand
Legendary
Offline
Activity: 2590
Merit: 3014
Welt Am Draht
|
|
November 12, 2014, 12:35:20 AM |
|
This coin was made from scratch inspired in NXT or uses their code changed? I saw that folder where are the data: C:\nxtl\db
It was originally going to be a NXT clone named nxt lite. It then became all new code along the way.
|
|
|
|
|