Bitcoin Forum
September 21, 2019, 03:33:20 AM *
News: If you like a topic and you see an orange "bump" link, click it. More info.
 
   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 ... 533 »
  Print  
Author Topic: Closed Thread  (Read 676380 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.
funnynews
Full Member
***
Offline Offline

Activity: 248
Merit: 100



View Profile
November 16, 2014, 05:41:33 PM
 #6941


OK, just to confirm, i can rest assured that my coins withdrawal will not go away? I can relax?

Would not it be better to deactivate withdraw until they migrate or no risk?


What is the state of your withdrawal on BTER? Completed, pending?

I think it is complete because the value subtracted from my balance and has a transaction ID:



The transaction is, but it does not hit the block, the coin remained in the account bter. I wrote bter 2 days ago they had to turn off the "Withdrawal" and said that we will turn off.

Write to them that the transaction did not hit the block at the time of renewal Peer

Edit Just contacted bter, said the problem. They said they take off contact solve the problem

Ok, thanks.

I saw now that the withdrawals were disabled.

I'll wait return the value to my account.

1569036800
Hero Member
*
Offline Offline

Posts: 1569036800

View Profile Personal Message (Offline)

Ignore
1569036800
Reply with quote  #2

1569036800
Report to moderator
1569036800
Hero Member
*
Offline Offline

Posts: 1569036800

View Profile Personal Message (Offline)

Ignore
1569036800
Reply with quote  #2

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

Activity: 1367
Merit: 1000


View Profile
November 16, 2014, 05:43:46 PM
 #6942

I do not understand Cry
Is the whole network down until new client? Huh
TheRealSilk
Sr. Member
****
Offline Offline

Activity: 457
Merit: 250


View Profile
November 16, 2014, 05:47:41 PM
 #6943

I do not understand Cry
Is the whole network down until new client? Huh

We have changed the version peer. When you run the older client connects to the main Peer startup. If the version does not meet then you will not be able to run the client

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

▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇ ▇ ▇
    ▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇
starik69
Legendary
*
Offline Offline

Activity: 1367
Merit: 1000


View Profile
November 16, 2014, 05:59:02 PM
 #6944

We have changed the version peer.
I do not understand Cry
What is "version peer"? Where it was changed? Huh
When you run the older client connects to the main Peer startup.
What means older? Older to what? Huh
What is "main Peer"? Where is it? Huh
If the version does not meet then you will not be able to run the client
What means "not be able to run the client"? How can i determine that? Huh
TheRealSilk
Sr. Member
****
Offline Offline

Activity: 457
Merit: 250


View Profile
November 16, 2014, 06:11:39 PM
 #6945

We have changed the version peer.
I do not understand Cry
What is "version peer"? Where it was changed? Huh
When you run the older client connects to the main Peer startup.
What means older? Older to what? Huh
What is "main Peer"? Where is it? Huh
If the version does not meet then you will not be able to run the client
What means "not be able to run the client"? How can i determine that? Huh

In order to avoid problems in network synchronization, all clients must be the same version
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.

We fix bugs, improve the module "transactions" and other modules. We need all clients worked correctly.
Peers that Nodes which when you first start the client connects and gets the whole list of other peers.  Now there are several of them , but we plan to grow the network to increase to main 100-200. Also, each running client on linux is peers, if we will make Your client IP on the linux client or windows client configuration by default , Your client IP will be the main peers.

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

▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇ ▇ ▇
    ▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇
starik69
Legendary
*
Offline Offline

Activity: 1367
Merit: 1000


View Profile
November 16, 2014, 07:08:15 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
martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


View Profile
November 16, 2014, 07:13:13 PM
 #6947

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?
TheRealSilk
Sr. Member
****
Offline Offline

Activity: 457
Merit: 250


View Profile
November 16, 2014, 07:30:47 PM
 #6948

Quote
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

Right until we test POA version must be the same

Quote
But it must be accepted by clients with the same version as mine? Roll Eyes
When the POA and transactions will work correctly and there are no errors, then You will be able to work with different versions

Quote
Are they hardcoded in the client? Huh

Yes, but it is temporary, in other versions You can choose their start peers when the final stable version clients and also add their peer

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

▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇ ▇ ▇
    ▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇
633android
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
November 16, 2014, 07:33:47 PM
 #6949

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?

I was going to ask the same question. Who decide what client must be used? Is the actual team development? and another question, how long does it take to decrease the numbers of Nodecoin (500,000) necessary to forging? and again who decide that?
Sorry for my English.
TheRealSilk
Sr. Member
****
Offline Offline

Activity: 457
Merit: 250


View Profile
November 16, 2014, 07:39:56 PM
 #6950

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

Edit While we're in beta, the main thing for us is identical version , later old clients will be able to work with new versions

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

▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇ ▇ ▇
    ▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇
TheRealSilk
Sr. Member
****
Offline Offline

Activity: 457
Merit: 250


View Profile
November 16, 2014, 07:45:49 PM
 #6951


I was going to ask the same question. Who decide what client must be used? Is the actual team development? and another question, how long does it take to decrease the numbers of Nodecoin (500,000) necessary to forging? and again who decide that?
Sorry for my English.

We decided therefore to protect investments by investors who did not sell their stakes. They will have an advantage in POA

When we integrate EUR-USD limitation will be removed

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

▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇ ▇ ▇
    ▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇▇
▇▇▇▇▇▇▇▇▇▇▇
martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


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

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?
TheRealSilk
Sr. Member
****
Offline Offline

Activity: 457
Merit: 250


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


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: 2114
Merit: 1237


Doomed to see the future and unable to prevent it


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

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.

adamavfc
Newbie
*
Offline Offline

Activity: 36
Merit: 0


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

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
 #6956


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
 #6957

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: 549
Merit: 251


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


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
 #6959


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
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250



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

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!

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