Bitcoin Forum
March 19, 2024, 08:50:19 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 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 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 ... 532 »
  Print  
Author Topic: Closed Thread  (Read 677630 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.
martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


View Profile
November 16, 2014, 07:48:44 PM
 #6941

In order to avoid problems in network synchronization, all clients must be the same version
You cannot control what other people do. In NXT i still see clients of 0.x.x  versions. Will NODE with different clients make their own network? Huh
What will happen if You are using an older version of the client, and I'm new. In our case, the transaction will not be accepted and will remain in your client, because the transaction is instant and the network must be synchronized continuously.
But it must be accepted by clients with the same version as mine? Roll Eyes
Now there are several of them , but we plan to grow the network to increase to main 100-200.
Are they hardcoded in the client? Huh

Are we centralized?

No, now the client works with 3-4 peers at the start to check the version, after which it connects to the following peers. Do you think if will not be the main peers and different versions of the clients the network to be divided into 2 or 3 parts

Will the configuration file. You will be able to add their own nodes . as well as all linux clients will be the main peers when will the final version

Sorry, didn't understand you well. Isn't it better to decide from which block fork will happen and old version clients will be on that fork or, from particular block, client will not work? Now it is thunder from the sky: no one client will work, wait for new client. This do not give trust for devs, devs can switch off all clients. I don't try to FUD, but this seems very bad for me. Maybe I missed something?
In order to achieve higher forum ranks, you need both activity points and merit points.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1710838219
Hero Member
*
Offline Offline

Posts: 1710838219

View Profile Personal Message (Offline)

Ignore
1710838219
Reply with quote  #2

1710838219
Report to moderator
1710838219
Hero Member
*
Offline Offline

Posts: 1710838219

View Profile Personal Message (Offline)

Ignore
1710838219
Reply with quote  #2

1710838219
Report to moderator
TheRealSilk
Sr. Member
****
Offline Offline

Activity: 457
Merit: 250


View Profile
November 16, 2014, 07:55:45 PM
 #6942


Sorry, didn't understand you well. Isn't it better to decide from which block fork will happen and old version clients will be on that fork or, from particular block, client will not work? Now it is thunder from the sky: no one client will work, wait for new client. This do not give trust for devs, devs can switch off all clients. I don't try to FUD, but this seems very bad for me. Maybe I missed something?

We have not disconnected clients, the clients have verification on version while we're in beta, had also been in the early stages and the community knows.
If the verification disable Your client to start and will work. But synchronization of the network will not work properly.

Edit When will the final version and will not be network errors , we disable the verification and you will be able to work as usual. You must understand we launched POA now the whole network to be checked for stability. we need a version of early

▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇ ▇ ▇
 
Instant Transactions
 
Non Bloating BlockChain
 

▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇ ▇ ▇
    ▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇
Hueristic
Legendary
*
Offline Offline

Activity: 3752
Merit: 4815


Doomed to see the future and unable to prevent it


View Profile
November 16, 2014, 08:00:58 PM
 #6943

In order to avoid problems in network synchronization, all clients must be the same version
You cannot control what other people do. In NXT i still see clients of 0.x.x  versions. Will NODE with different clients make their own network? Huh
What will happen if You are using an older version of the client, and I'm new. In our case, the transaction will not be accepted and will remain in your client, because the transaction is instant and the network must be synchronized continuously.
But it must be accepted by clients with the same version as mine? Roll Eyes
Now there are several of them , but we plan to grow the network to increase to main 100-200.
Are they hardcoded in the client? Huh

Are we centralized?

No, now the client works with 3-4 peers at the start to check the version, after which it connects to the following peers. Do you think if will not be the main peers and different versions of the clients the network to be divided into 2 or 3 parts

Will the configuration file. You will be able to add their own nodes . as well as all linux clients will be the main peers when will the final version

Sorry, didn't understand you well. Isn't it better to decide from which block fork will happen and old version clients will be on that fork or, from particular block, client will not work? Now it is thunder from the sky: no one client will work, wait for new client. This do not give trust for devs, devs can switch off all clients. I don't try to FUD, but this seems very bad for me. Maybe I missed something?

YES, You missed "BETA" status. These are precautionary measure in place until final release candidate.

“Bad men need nothing more to compass their ends, than that good men should look on and do nothing.”
adamavfc
Newbie
*
Offline Offline

Activity: 36
Merit: 0


View Profile
November 16, 2014, 08:01:38 PM
 #6944

I have set up a new twitter account if anyone wants to follow it. I will try and take key details out from this thread and get tweeted quickly.

https://twitter.com/NodeCoinUpdates
martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


View Profile
November 16, 2014, 08:02:32 PM
 #6945


Sorry, didn't understand you well. Isn't it better to decide from which block fork will happen and old version clients will be on that fork or, from particular block, client will not work? Now it is thunder from the sky: no one client will work, wait for new client. This do not give trust for devs, devs can switch off all clients. I don't try to FUD, but this seems very bad for me. Maybe I missed something?

We have not disconnected clients, the clients have verification on version while we're in beta, had also been in the early stages and the community knows.
If the verification disable Your client to start and will work. But synchronization of the network will not work properly.

Edit When will the final version and will not be network errors , we disable the verification and you will be able to work as usual. You must understand we launched POA now the whole network to be checked for stability. we need a version of early

Yes, I understand, that NODE is in early state, but in future, things like it happened today should be informed before. People will start panic.

P.S. I'm not panicking at all, but IMO it was not right approach Smiley
martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


View Profile
November 16, 2014, 08:07:16 PM
 #6946

In order to avoid problems in network synchronization, all clients must be the same version
You cannot control what other people do. In NXT i still see clients of 0.x.x  versions. Will NODE with different clients make their own network? Huh
What will happen if You are using an older version of the client, and I'm new. In our case, the transaction will not be accepted and will remain in your client, because the transaction is instant and the network must be synchronized continuously.
But it must be accepted by clients with the same version as mine? Roll Eyes
Now there are several of them , but we plan to grow the network to increase to main 100-200.
Are they hardcoded in the client? Huh

Are we centralized?

No, now the client works with 3-4 peers at the start to check the version, after which it connects to the following peers. Do you think if will not be the main peers and different versions of the clients the network to be divided into 2 or 3 parts

Will the configuration file. You will be able to add their own nodes . as well as all linux clients will be the main peers when will the final version

Sorry, didn't understand you well. Isn't it better to decide from which block fork will happen and old version clients will be on that fork or, from particular block, client will not work? Now it is thunder from the sky: no one client will work, wait for new client. This do not give trust for devs, devs can switch off all clients. I don't try to FUD, but this seems very bad for me. Maybe I missed something?

YES, You missed "BETA" status. These are precautionary measure in place until final release candidate.

I know, its BETA, but Node's are real Smiley
fedoralite
Sr. Member
****
Offline Offline

Activity: 548
Merit: 251


View Profile
November 16, 2014, 08:12:13 PM
 #6947


I know, its BETA, but Node's are real Smiley

You probably missed the project Crypti, almost every day the network was not working.
martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


View Profile
November 16, 2014, 08:25:39 PM
 #6948


I know, its BETA, but Node's are real Smiley

You probably missed the project Crypti, almost every day the network was not working.

I don't care about Crypti, I care about NODE. We aren't following bad examples, are we? Smiley
koop4u (OP)
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250



View Profile
November 16, 2014, 09:20:53 PM
 #6949

Quote
Yes, I understand, that NODE is in early state, but in future, things like it happened today should be informed before. People will start panic.

P.S. I'm not panicking at all, but IMO it was not right approach Smiley

Acknowledged, thank you for your continuous support and understanding! We'll do it properly next time!


I know, its BETA, but Node's are real Smiley

You probably missed the project Crypti, almost every day the network was not working.

I don't care about Crypti, I care about NODE. We aren't following bad examples, are we? Smiley

We are not! And you are right, those NODES are real, and since the launch of the Beta version 0.1 till current 0.9b, NO  collapses had occurred! Which i think deserves credit!

martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


View Profile
November 16, 2014, 09:30:54 PM
 #6950

Quote
Yes, I understand, that NODE is in early state, but in future, things like it happened today should be informed before. People will start panic.

P.S. I'm not panicking at all, but IMO it was not right approach Smiley

Acknowledged, thank you for your continuous support and understanding! We'll do it properly next time!


I know, its BETA, but Node's are real Smiley

You probably missed the project Crypti, almost every day the network was not working.

I don't care about Crypti, I care about NODE. We aren't following bad examples, are we? Smiley

We are not! And you are right, those NODES are real, and since the launch of the Beta version 0.1 till current 0.9b, NO  collapses had occurred! Which i think deserves credit!

I respect work of devs, no doubt about that. Just this time, when clients were "switched off the game" without announcement, was not good approach. That's only my opinion Smiley

In any case, let's move forward Smiley
Grillo
Full Member
***
Offline Offline

Activity: 225
Merit: 100



View Profile
November 16, 2014, 09:44:23 PM
 #6951

Node will be in the top 20 in 2 month.
xibeijan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001


View Profile
November 16, 2014, 09:58:11 PM
 #6952

ИODE only produces new blocks when transactions appear.  How does Node protect its blockchain without mining blocks continuously?

An attacker could quickly forge an alternative blockchain and easily overtake a stagnant main chain.

Notable projects 2019: Semux, Dero, Wagerr, BEAM
starik69
Legendary
*
Offline Offline

Activity: 1367
Merit: 1000


View Profile
November 16, 2014, 10:24:28 PM
 #6953

Are devs using different clients compared to those provided for public?  Huh
LemonAndFries
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250


View Profile
November 16, 2014, 10:43:34 PM
 #6954

Quote
Yes, I understand, that NODE is in early state, but in future, things like it happened today should be informed before. People will start panic.

P.S. I'm not panicking at all, but IMO it was not right approach Smiley

Acknowledged, thank you for your continuous support and understanding! We'll do it properly next time!


I know, its BETA, but Node's are real Smiley

You probably missed the project Crypti, almost every day the network was not working.

I don't care about Crypti, I care about NODE. We aren't following bad examples, are we? Smiley

We are not! And you are right, those NODES are real, and since the launch of the Beta version 0.1 till current 0.9b, NO  collapses had occurred! Which i think deserves credit!

I respect work of devs, no doubt about that. Just this time, when clients were "switched off the game" without announcement, was not good approach. That's only my opinion Smiley

In any case, let's move forward Smiley

There was actually a quick mention Dev did last week that over the weekend they were going to switch clients and asked bter to disable deposits\withdrawals for this.
xibeijan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001


View Profile
November 16, 2014, 10:54:39 PM
 #6955

ИODE only produces new blocks when transactions appear.  How does Node protect its blockchain without mining blocks continuously?

An attacker could quickly forge an alternative blockchain and easily overtake a stagnant main chain.

Notable projects 2019: Semux, Dero, Wagerr, BEAM
Hueristic
Legendary
*
Offline Offline

Activity: 3752
Merit: 4815


Doomed to see the future and unable to prevent it


View Profile
November 16, 2014, 10:57:00 PM
 #6956

ИODE only produces new blocks when transactions appear.  How does Node protect its blockchain without mining blocks continuously?

An attacker could quickly forge an alternative blockchain and easily overtake a stagnant main chain.

Go ahead and try. Smiley

They will not answer your questions like this until the coin is out of beta and the code is open sourced. And I support them in this.

“Bad men need nothing more to compass their ends, than that good men should look on and do nothing.”
jwilford
Full Member
***
Offline Offline

Activity: 123
Merit: 100


View Profile
November 16, 2014, 11:09:50 PM
 #6957

ИODE only produces new blocks when transactions appear.  How does Node protect its blockchain without mining blocks continuously?

An attacker could quickly forge an alternative blockchain and easily overtake a stagnant main chain.

I am not a DEV so I can only conjecture but I would imagine since they would only have their own personal private keys and not the rest that they would only be able to send transactions out of their accounts and not in to them. Since POA is not a race but a lottery I would not see any advantage to forging a bunch of fake blocks where you send your own money out since if you succeeded the rest of the network would quickly catch up to you and continue on and the only thing you would accomplish is spending your own NODE which the network allows for anyway. If you fail you risk getting exposed and your node getting blacklisted. Again not a DEV so maybe I am completely wrong but from my reading of PoA I can see no economic advantage since like I said earlier it is no longer a race as to who can create more blocks. BTW I also support the devs in not answering until the code comes out but I'm glad you asked in case there is a real issue that needs to be looked at.

EDIT I assume you were only talking about forging your own chain for purposes of getting ahead of the rest of the nodes and trying to double spend right? The only two reasons I could see for doing that would be double spending or trying to crash the value of NODE by scaring people but the second begs the question of why would you invest so much just to crash your own assets?
iHashFury
Full Member
***
Offline Offline

Activity: 141
Merit: 100


View Profile
November 16, 2014, 11:28:45 PM
 #6958

Should I leave my node running or kill it?

Code:
forever stop index.js

LemonAndFries
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250


View Profile
November 17, 2014, 12:28:43 AM
 #6959

Should I leave my node running or kill it?

Code:
forever stop index.js



Your call but wait for update of new client.

Old clients cannot connect to network ATM.
yambad
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
November 17, 2014, 01:53:45 AM
 #6960

ИODE only produces new blocks when transactions appear.  How does Node protect its blockchain without mining blocks continuously?

An attacker could quickly forge an alternative blockchain and easily overtake a stagnant main chain.

I am not a DEV so I can only conjecture but I would imagine since they would only have their own personal private keys and not the rest that they would only be able to send transactions out of their accounts and not in to them. Since POA is not a race but a lottery I would not see any advantage to forging a bunch of fake blocks where you send your own money out since if you succeeded the rest of the network would quickly catch up to you and continue on and the only thing you would accomplish is spending your own NODE which the network allows for anyway. If you fail you risk getting exposed and your node getting blacklisted. Again not a DEV so maybe I am completely wrong but from my reading of PoA I can see no economic advantage since like I said earlier it is no longer a race as to who can create more blocks. BTW I also support the devs in not answering until the code comes out but I'm glad you asked in case there is a real issue that needs to be looked at.

EDIT I assume you were only talking about forging your own chain for purposes of getting ahead of the rest of the nodes and trying to double spend right? The only two reasons I could see for doing that would be double spending or trying to crash the value of NODE by scaring people but the second begs the question of why would you invest so much just to crash your own assets?

WTF, pass me the contact of his drug supplier, should be good.
Pages: « 1 ... 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 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 ... 532 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!