Topic: . - page 67. (Read 491736 times)
Good time to buy if you can spare the funds...
May be.. Who is the last? 
When distribution is over?
Good time to buy if you can spare the funds...
May be.. Who is the last? 
Non-payment of all nodes. Failure ...
Delayed, but they are aware of it and resolving it. Long as you are updated you should be fine.
Community is starved of news and updates. Let's see what you have for us now. A month is plenty of time between forks, and let's be honest.... really a month or expected a month and realistically two or maybe three if you have issues?
Agree.
There is no need to hurry up. We need a steady development process - V4, then V5.
I think it's better upgrade to V4 now and postpone V5 for two monthes (to a back-to-school season
) than wait a month for v4. Node script is being worked on. We moved a lot of things to new servers, and CBKR is on it.
Is it on github?
Negative.
I've just been informed that that the node bounty payout will happen manually tonight. As the script is still in test mode, there will be only one transaction per account and the node addressess and amounts will be in the transaction message.
This will hopefully sort out all problems we were having with the bounty transactions.
This will hopefully sort out all problems we were having with the bounty transactions.
Sounds great, I'm looking forward...
Question to the community: HZ 4.0 is complete, and we have 5.0 on test net. Both updates would require hard forks, and we would like to keep these forks to a minimum, so we are asking the community if we should release 4.0 and go through a hard fork, or wait another month and have 1 hard fork for 5.0 which will introduce the voting and monetary features, as well as a slew of others.
V4 release now, V5 later.
Question to the community: HZ 4.0 is complete, and we have 5.0 on test net. Both updates would require hard forks, and we would like to keep these forks to a minimum, so we are asking the community if we should release 4.0 and go through a hard fork, or wait another month and have 1 hard fork for 5.0 which will introduce the voting and monetary features, as well as a slew of others.
Let's do firstly release 4.0, and then easy go on rel 5.0my opinion...
Question to the community: HZ 4.0 is complete, and we have 5.0 on test net. Both updates would require hard forks, and we would like to keep these forks to a minimum, so we are asking the community if we should release 4.0 and go through a hard fork, or wait another month and have 1 hard fork for 5.0 which will introduce the voting and monetary features, as well as a slew of others.
Let's do firstly release 4.0, and then easy go on rel 5.0my opinion...
Question to the community: HZ 4.0 is complete, and we have 5.0 on test net. Both updates would require hard forks, and we would like to keep these forks to a minimum, so we are asking the community if we should release 4.0 and go through a hard fork, or wait another month and have 1 hard fork for 5.0 which will introduce the voting and monetary features, as well as a slew of others.
Jump to: