So decision was taken
But you do not know how to implement it?
Topic: [ANN] Ħ [HODL] 5% Interest. No Staking Req. Term Deposits 10%. Solo Mining. - page 101. (Read 472950 times)
February 03, 2017, 08:00:41 AM
February 01, 2017, 07:11:03 PM
So just to be sure. Current version is 2.0 of wallet?
No hard fork and unlock mined coins?
No hard fork and unlock mined coins?
Yes v2.0.
There was a nutocracy vote that passed (https://nutocracy.herokuapp.com/arguments/29) but no hard fork (hard unfork?) has been coded/submitted/tested/etc to that end.
February 01, 2017, 04:10:58 PM
So just to be sure. Current version is 2.0 of wallet?
No hard fork and unlock mined coins?
No hard fork and unlock mined coins?
February 01, 2017, 11:38:34 AM
I locked my coins in 365days deposit in May 2016 but now estimated maturation date is 10-11/2017 O.o
i remember that the more later you lock your funds since the coin started the more time you need for maturation, so your 365 days are more than that now, this was done as a deterrent to prevent that everyone will only lock the deposit and don't buy anything on the market
February 01, 2017, 11:34:09 AM
I locked my coins in 365days deposit in May 2016 but now estimated maturation date is 10-11/2017 O.o
hmmmmmmmm... ikt is only your estimation just and not fix figure for it.
I think, the locking period isnt calculated by dates, its calculated by the expected amount of blocks at the moment, where u locked. One year is a very long time, and if one month the chain moved slowlier than expected, the date is shifting...
Greetz
Steve
February 01, 2017, 07:39:55 AM
I locked my coins in 365days deposit in May 2016 but now estimated maturation date is 10-11/2017 O.o
hmmmmmmmm... ikt is only your estimation just and not fix figure for it.
February 01, 2017, 03:18:33 AM
Not seeing anyone jumping in on this. Freetrade/Fuzzbawls, are you willing to do the work that needs to be done?
I'm currently overwhelmed with other work at the moment but will see if I can schedule some time to write the fork code in a couple weeks.
If you really want to unfork, simply run the old version on a server, announce the IP and start mining, right? I never updated and have the old chain up to September 2016.
no...just...no
Very much appreciate it.
January 31, 2017, 06:58:07 PM
Not seeing anyone jumping in on this. Freetrade/Fuzzbawls, are you willing to do the work that needs to be done?
I'm currently overwhelmed with other work at the moment but will see if I can schedule some time to write the fork code in a couple weeks.
If you really want to unfork, simply run the old version on a server, announce the IP and start mining, right? I never updated and have the old chain up to September 2016.
no...just...no
January 31, 2017, 03:23:14 PM
If you really want to unfork, simply run the old version on a server, announce the IP and start mining, right? I never updated and have the old chain up to September 2016.
January 31, 2017, 03:03:00 PM
why not asking limxdev? he is skilled enough for timedepositcoins, because he coded europecoin very well!
Greetz
Steve
Greetz
Steve
January 31, 2017, 02:27:49 PM
I am willing to learn the dev role and then apply ~5hrs/wk to helping out. I would just need some hand-holding to get ramped up.
This is probably only helpful in the following situation: there is someone who knows how to do it or can explain the syntax of the code, but they don't have enough time or desire to do the fix, but they are willing to spend a small amount of time showing me the ropes.
I have limited web-dev and python experience so I can understand the logical flow but I have never written any code for a crypto project.
Let me know if this helps at all. Otherwise, maybe I can just add some hash power at whatever point that is helpful.
Carry on.
This is probably only helpful in the following situation: there is someone who knows how to do it or can explain the syntax of the code, but they don't have enough time or desire to do the fix, but they are willing to spend a small amount of time showing me the ropes.
I have limited web-dev and python experience so I can understand the logical flow but I have never written any code for a crypto project.
Let me know if this helps at all. Otherwise, maybe I can just add some hash power at whatever point that is helpful.
Carry on.
January 31, 2017, 03:07:11 AM
Not seeing anyone jumping in on this. Freetrade/Fuzzbawls, are you willing to do the work that needs to be done?
I'm volunteering to do the term deposit bug fix if someone else is leading a hard fork.
January 31, 2017, 02:22:21 AM
So here's a question from a non-dev-type (me). We were rolling along on Version 1 of the wallet/miner. We hard-forked to Version 2. We now want to un-fork (or fork again if that is more appropriate). If we changed nothing in terms of the bug fix or optimizations (for the moment), could we not simply use Version 1 again? And if that's possible, would the bug fix and optimizations be able to be put in to the wallet later without it being a dramatic fork?
Interesting - you could try running version 1 to see if it accepts the current chain - if it does, it may well be possible to use it.
I installed Ver 1 but it just sits with "No block source available, 51 weeks behind"
As part of the previous fork, v1 clients were no longer allowed on the network. Mainly to reduce overhead in rejecting invalid blocks.
ah right. So maybe if he gives a v1 client the current blockchain, it could accept it and then be able to communicate with other v1 clients in a similar situation. Would be pretty hacky though.
Not seeing anyone jumping in on this. Freetrade/Fuzzbawls, are you willing to do the work that needs to be done?
January 29, 2017, 04:28:57 AM
I locked my coins in 365days deposit in May 2016 but now estimated maturation date is 10-11/2017 O.o
January 28, 2017, 05:06:35 AM
So here's a question from a non-dev-type (me). We were rolling along on Version 1 of the wallet/miner. We hard-forked to Version 2. We now want to un-fork (or fork again if that is more appropriate). If we changed nothing in terms of the bug fix or optimizations (for the moment), could we not simply use Version 1 again? And if that's possible, would the bug fix and optimizations be able to be put in to the wallet later without it being a dramatic fork?
Interesting - you could try running version 1 to see if it accepts the current chain - if it does, it may well be possible to use it.
I installed Ver 1 but it just sits with "No block source available, 51 weeks behind"
As part of the previous fork, v1 clients were no longer allowed on the network. Mainly to reduce overhead in rejecting invalid blocks.
ah right. So maybe if he gives a v1 client the current blockchain, it could accept it and then be able to communicate with other v1 clients in a similar situation. Would be pretty hacky though.
January 28, 2017, 04:14:20 AM
So here's a question from a non-dev-type (me). We were rolling along on Version 1 of the wallet/miner. We hard-forked to Version 2. We now want to un-fork (or fork again if that is more appropriate). If we changed nothing in terms of the bug fix or optimizations (for the moment), could we not simply use Version 1 again? And if that's possible, would the bug fix and optimizations be able to be put in to the wallet later without it being a dramatic fork?
Interesting - you could try running version 1 to see if it accepts the current chain - if it does, it may well be possible to use it.
I installed Ver 1 but it just sits with "No block source available, 51 weeks behind"
As part of the previous fork, v1 clients were no longer allowed on the network. Mainly to reduce overhead in rejecting invalid blocks.
January 28, 2017, 04:09:36 AM
So here's a question from a non-dev-type (me). We were rolling along on Version 1 of the wallet/miner. We hard-forked to Version 2. We now want to un-fork (or fork again if that is more appropriate). If we changed nothing in terms of the bug fix or optimizations (for the moment), could we not simply use Version 1 again? And if that's possible, would the bug fix and optimizations be able to be put in to the wallet later without it being a dramatic fork?
Interesting - you could try running version 1 to see if it accepts the current chain - if it does, it may well be possible to use it.
I installed Ver 1 but it just sits with "No block source available, 51 weeks behind"
January 28, 2017, 02:09:10 AM
So here's a question from a non-dev-type (me). We were rolling along on Version 1 of the wallet/miner. We hard-forked to Version 2. We now want to un-fork (or fork again if that is more appropriate). If we changed nothing in terms of the bug fix or optimizations (for the moment), could we not simply use Version 1 again? And if that's possible, would the bug fix and optimizations be able to be put in to the wallet later without it being a dramatic fork?
Interesting - you could try running version 1 to see if it accepts the current chain - if it does, it may well be possible to use it.
January 27, 2017, 02:47:06 PM
I would have thought you could, but would the old version one act strange if it saw on the chain blocks which before it would not have done?
January 27, 2017, 02:19:46 PM
What's the next step and who has the ability to take it? If we're hard forking away from the auto-hodl, and if that means requiring a new wallet/miner (3.0?), is this the time to get the optiminer improvements into the wallet? I think @Fuzzbawls might have been working on that, is that still the case? @Freetrade also mentioned that getting those improvements into the wallet miner was perhaps the most important next step.
The central question would then be, do we charge ahead with removing auto-hodl and worry about the wallet improvements later or wait and do both at the same time?
All I have is questions, does anyone have any answers?
I think, at a minimum -
1. Fork code update (most coin devs could handle this)
2. Bug code fix (I've volunteered to do this)
3. New Wallet Binaries Compiled (Fuzz has handled this in the past)
4. Yobit update (may require payment)
nice to have
5. Wallet mining optimizations (what Fuzz showed me was probably 90% there)
Excellent thank you.
Ok, so it looks like we need a coin dev to work with Fuzzbawls and Freetrade on the pieces and parts, assuming Fuzzbawls is willing, are you Fuzz? Is there someone who would like to step up to the role of coding the new fork, integrating Freetrade's fix, and perhaps integrating the wallet optimizations?
We are certainly appreciative of anyone who is, has, or will donate their time and expertise to the project. However, dev's do like to see some consideration for the hard work they do and the time they put in and we don't want to proceed with the assumption that everything is going to be done for free. What would be appropriate bounties to provide for everything in Freetrade's list?
So here's a question from a non-dev-type (me). We were rolling along on Version 1 of the wallet/miner. We hard-forked to Version 2. We now want to un-fork (or fork again if that is more appropriate). If we changed nothing in terms of the bug fix or optimizations (for the moment), could we not simply use Version 1 again? And if that's possible, would the bug fix and optimizations be able to be put in to the wallet later without it being a dramatic fork?
Jump to: