martismartis
Legendary
Offline
Activity: 1162
Merit: 1005
|
|
November 16, 2014, 07:48:44 PM |
|
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? 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? 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? 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?
|
|
|
|
TheRealSilk
|
|
November 16, 2014, 07:55:45 PM |
|
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
|
|
|
|
Hueristic
Legendary
Offline
Activity: 3948
Merit: 5363
Doomed to see the future and unable to prevent it
|
|
November 16, 2014, 08:00:58 PM |
|
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? 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? 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? 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
Activity: 36
Merit: 0
|
|
November 16, 2014, 08:01:38 PM |
|
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
Activity: 1162
Merit: 1005
|
|
November 16, 2014, 08:02:32 PM |
|
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
|
|
|
|
martismartis
Legendary
Offline
Activity: 1162
Merit: 1005
|
|
November 16, 2014, 08:07:16 PM |
|
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? 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? 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? 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
|
|
|
|
fedoralite
|
|
November 16, 2014, 08:12:13 PM |
|
I know, its BETA, but Node's are real You probably missed the project Crypti, almost every day the network was not working.
|
|
|
|
martismartis
Legendary
Offline
Activity: 1162
Merit: 1005
|
|
November 16, 2014, 08:25:39 PM |
|
I know, its BETA, but Node's are real 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?
|
|
|
|
koop4u (OP)
|
|
November 16, 2014, 09:20:53 PM |
|
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 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 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? 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
Activity: 1162
Merit: 1005
|
|
November 16, 2014, 09:30:54 PM |
|
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 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 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? 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 In any case, let's move forward
|
|
|
|
Grillo
|
|
November 16, 2014, 09:44:23 PM |
|
Node will be in the top 20 in 2 month.
|
|
|
|
xibeijan
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
November 16, 2014, 09:58:11 PM |
|
И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.
|
|
|
|
starik69
Legendary
Offline
Activity: 1367
Merit: 1000
|
|
November 16, 2014, 10:24:28 PM |
|
Are devs using different clients compared to those provided for public?
|
|
|
|
LemonAndFries
|
|
November 16, 2014, 10:43:34 PM |
|
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 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 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? 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 In any case, let's move forward 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
Activity: 1232
Merit: 1001
|
|
November 16, 2014, 10:54:39 PM |
|
И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.
|
|
|
|
Hueristic
Legendary
Offline
Activity: 3948
Merit: 5363
Doomed to see the future and unable to prevent it
|
|
November 16, 2014, 10:57:00 PM |
|
И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. 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
|
|
November 16, 2014, 11:09:50 PM |
|
И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
|
|
November 16, 2014, 11:28:45 PM |
|
Should I leave my node running or kill it?
|
|
|
|
LemonAndFries
|
|
November 17, 2014, 12:28:43 AM |
|
Should I leave my node running or kill it? Your call but wait for update of new client. Old clients cannot connect to network ATM.
|
|
|
|
yambad
|
|
November 17, 2014, 01:53:45 AM |
|
И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.
|
|
|
|
|