Bitcoin Forum
August 22, 2019, 10:48:32 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 [328] 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 ... 533 »
  Print  
Author Topic: Closed Thread  (Read 676379 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Hueristic
Legendary
*
Offline Offline

Activity: 2086
Merit: 1225


Doomed to see the future and unable to prevent it


View Profile
November 11, 2014, 11:36:56 PM
 #6541

Wallet stuck. Tried twice.

Quote
Loading ... Please wait!
Download blocks start. Download block at height: 3382

1566470912
Hero Member
*
Offline Offline

Posts: 1566470912

View Profile Personal Message (Offline)

Ignore
1566470912
Reply with quote  #2

1566470912
Report to moderator
1566470912
Hero Member
*
Offline Offline

Posts: 1566470912

View Profile Personal Message (Offline)

Ignore
1566470912
Reply with quote  #2

1566470912
Report to moderator
1566470912
Hero Member
*
Offline Offline

Posts: 1566470912

View Profile Personal Message (Offline)

Ignore
1566470912
Reply with quote  #2

1566470912
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1566470912
Hero Member
*
Offline Offline

Posts: 1566470912

View Profile Personal Message (Offline)

Ignore
1566470912
Reply with quote  #2

1566470912
Report to moderator
GreenDude
Hero Member
*****
Offline Offline

Activity: 531
Merit: 500


View Profile
November 11, 2014, 11:50:46 PM
 #6542

Wallet stuck. Tried twice.

Quote
Loading ... Please wait!
Download blocks start. Download block at height: 3382

Im on block 3387
kripto
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
November 11, 2014, 11:53:03 PM
 #6543

Wallet stuck. Tried twice.

Quote
Loading ... Please wait!
Download blocks start. Download block at height: 3382

Im on block 3387

so am i
jwilford
Full Member
***
Offline Offline

Activity: 123
Merit: 100


View Profile
November 12, 2014, 12:01:06 AM
 #6544

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.  Smiley
Hueristic
Legendary
*
Offline Offline

Activity: 2086
Merit: 1225


Doomed to see the future and unable to prevent it


View Profile
November 12, 2014, 12:06:37 AM
 #6545

Wallet stuck. Tried twice.

Quote
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. Smiley

GreenDude
Hero Member
*****
Offline Offline

Activity: 531
Merit: 500


View Profile
November 12, 2014, 12:15:06 AM
 #6546

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

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
Hero Member
*****
Offline Offline

Activity: 531
Merit: 500


View Profile
November 12, 2014, 12:18:46 AM
 #6547

Anyway u could go back and find this discussion already made by patmast3r and silkk and another guys already if u have doubts.
jwilford
Full Member
***
Offline Offline

Activity: 123
Merit: 100


View Profile
November 12, 2014, 12:27:22 AM
 #6548

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

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
Full Member
***
Offline Offline

Activity: 123
Merit: 100


View Profile
November 12, 2014, 12:29:13 AM
 #6549

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.  Smiley
rramires
Full Member
***
Offline Offline

Activity: 231
Merit: 100



View Profile
November 12, 2014, 12:33:07 AM
 #6550

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
*
Online Online

Activity: 2100
Merit: 1914


Your dearest bum chum


View Profile
November 12, 2014, 12:35:20 AM
 #6551

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.

GreenDude
Hero Member
*****
Offline Offline

Activity: 531
Merit: 500


View Profile
November 12, 2014, 12:36:37 AM
 #6552

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

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.

My address is the one ending in 566.. I forged about 50 nodes today which is nothing.. But yes.. I forged early today and after that didn't anymore. I just logout and logged in again because probably there was a mistake with my connection. As i understand if there is a problem with some NODE the system will skip it and look for the next one. I dont know what could cause this.. Right now i'm living in a place where ie connection is bad so i can't be sure about it.
jwilford
Full Member
***
Offline Offline

Activity: 123
Merit: 100


View Profile
November 12, 2014, 12:40:32 AM
 #6553

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

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.

My address is the one ending in 566.. I forged about 50 nodes today which is nothing.. But yes.. I forged early today and after that didn't anymore. I just logout and logged in again because probably there was a mistake with my connection. As i understand if there is a problem with some NODE the system will skip it and look for the next one. I dont know what could cause this.. Right now i'm living in a place where ie connection is bad so i can't be sure about it.

I could believe that my connection faltered at some point today too. It would be really useful if we could see our own nodeheight or at least a status of some kind so we could know when there is a problem that is causing us to get left out.
GreenDude
Hero Member
*****
Offline Offline

Activity: 531
Merit: 500


View Profile
November 12, 2014, 12:43:17 AM
 #6554

Yes. It would be really useful to be possible to see own nodeheight.
PoulGrym
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
November 12, 2014, 12:55:33 AM
 #6555

I got stuck today as well, then just logged out and in again made my first forge. We really need to have some sort of connection check routine going. I had lost peer connections.

If you found my post helpful, use my tip jar!
BTC: 1Q4um62DJ8kBRMzQ4VQqG6W7eLoPNfx6zn
NODE: 11993447274130959091 NXT: MINT:
rramires
Full Member
***
Offline Offline

Activity: 231
Merit: 100



View Profile
November 12, 2014, 01:02:44 AM
 #6556

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.

Nice, I bought a little in Bter, simply send to client and maintaining open for to forge?
jwilford
Full Member
***
Offline Offline

Activity: 123
Merit: 100


View Profile
November 12, 2014, 01:04:25 AM
 #6557

I got stuck today as well, then just logged out and in again made my first forge. We really need to have some sort of connection check routine going. I had lost peer connections.

Well I guess this whole discussion blows my previous theory out of the water. It seems that there is some method for determining if a node is active and it is sensitive. Well if there needs to be an update I would rather it need to be something that makes it harder to forge than easier to game.
jwilford
Full Member
***
Offline Offline

Activity: 123
Merit: 100


View Profile
November 12, 2014, 01:18:16 AM
 #6558

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.

Nice, I bought a little in Bter, simply send to client and maintaining open for to forge?

You will need 500k Node in your wallet to forge but yes.
gomei
Hero Member
*****
Offline Offline

Activity: 770
Merit: 500



View Profile
November 12, 2014, 02:38:28 AM
 #6559

Node is way undervalued!
yes, the it's smart to hold on some node when it is cheap.

.Ambit.    ██
██  ██
██  ██
██  ██
██  ██
██  ██
██  ██
██  ██
██  ██
██  ██
██  █████
██
████████████
   Become part of the mining family   
✔ SECURED  │ WHITEPAPER │  ★ 171% ROI
██   
██  ██
██  ██
██  ██
██  ██
██  ██
██  ██
██  ██
██  ██
██  ██
█████  ██
██
████████████
ThomasZ80
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
November 12, 2014, 06:53:44 AM
 #6560

No Coins left to buy on BTER? Wow.  Shocked
Price will continue to rise.
Pages: « 1 ... 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 [328] 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 ... 533 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!