i really have no idea how to fix the syncing issue to be quite honest. The best i can do is attempt to port ADT to another coin's source. So if anyone has some suggestions on a rock solid, fast PoS time coin plz tell.
About the Staking changes. I've never done anything like it. But as always i can try and give it a shot using another hard fork from another coin as a comparison. So again ideas please
Ahmed
Topic: [ANN] Androids Tokens v2.0 [Proof of Stake] - page 17. (Read 115867 times)
I am happy to donate the BTC I gave eexchanger and some more ADT to whoever fixes it just get it done finally.
that's good to hear but is anyone actually capable of doing something to get this finally on track?
i think ahmed could if he put his mind to it as he is very good at what he does he just hasent had much experence in POS coins
that's good to hear but is anyone actually capable of doing something to get this finally on track?
Since you are keeping watch, what is next on the agenda?
-tb-
-tb-
geting a patch sorted so that big wallets dont cause forks and hopfuly imploment the new POS prameters that were meant to take afect at block 100k
Since you are keeping watch, what is next on the agenda?
-tb-
-tb-
so is there any hope? Ahmed? Zack have you really left us?
i am still here i just have a lot of stuff going on at the moment i am keeping watch of this thread and replying to all pms and skype messages
so is there any hope? Ahmed? Zack have you really left us?
any real development or is this being abandoned now?
Who knows. Zack isn't around anymore. Time for someone else to take over. I don't have the time nor qualifications to.
any real development or is this being abandoned now?
The main problem here is that the Staking is too far out so no one is Staking their Coins and Zack doesn't want to open up the wallet with large amount of coins because it will Stake at maximum weight all at once and cause a fork.
Wouldn't setting reservebalance to (total_balance - smallest_unspent_output) generate a maximum of one PoS block? And continue gradually reducing the reserve if weight is insufficient. Unless there's only a few gigantic unspent outputs rather than multiple smaller ones?
BTW, I presume the 100k hard fork has been postponed?
No, I mean that the minimum Stake is 15 days so people forget about it and keep their Wallets closed and so with a minimum amount of reward is so small that there is no incentive in order to have your coins in your wallet and Staking so network security becomes low and localized into clusters of coins Staking all at once and with POW mining also with small incentive and Staking before being synced, there are a number of issues here at work. A fork could be created by shunting POS Blocks until it becomes POW only and then have a majority of the hashrate.
(total_balance - smallest_unspent_output) wouldn't really work unless you were over the maximum stake period and alot of coins are often so small that they will never Stake, your smallest unspent output in this case could be dust. It would probably be better something along the lines of (total_balance - (smallest_unspent_output > 1000 * COIN))
Would it continually produce just one POS? I think it would just unlock one block unless scripted to do so, you should try this and tell us how you go with it.
The main problem here is that the Staking is too far out so no one is Staking their Coins and Zack doesn't want to open up the wallet with large amount of coins because it will Stake at maximum weight all at once and cause a fork.
Wouldn't setting reservebalance to (total_balance - smallest_unspent_output) generate a maximum of one PoS block? And continue gradually reducing the reserve if weight is insufficient. Unless there's only a few gigantic unspent outputs rather than multiple smaller ones?
BTW, I presume the 100k hard fork has been postponed?
didnt sync at all although it connected to peers. need to figure out why but havent had much free time recently
bitcoin seeder
seeder shouldnt stop the client from downloading blocks
Connecting to nodes on a lower Blockchain does stop it from downloading blocks as well as being able to stake before being fully synced.
Setup 5-6 more nodes, edit the list to only include the trusted nodes, set up seed nodes, reduce the Staking deviation time from 2 hours to 10 minutes, make the client not stake unless fully synced and possibly even remove the POW altogether since it's a security risk.
The main problem here is that the Staking is too far out so no one is Staking their Coins and Zack doesn't want to open up the wallet with large amount of coins because it will Stake at maximum weight all at once and cause a fork.
You could send coins to private nodes to Stake and run the network and tunnel in through SSH, each transaction represents a block of coins that will Stake once matured so Zack could use his transaction program to equalize the Staking and have those coins helping to run the network.
You also need coin control, it's pretty much essential to Proof of Stake so you can manage all your blocks of coins so that you don't have thousands of small transactions all trying to hash their stake, not succeeding and slowing down your system.
didnt sync at all although it connected to peers. need to figure out why but havent had much free time recently
bitcoin seeder
seeder shouldnt stop the client from downloading blocks
didnt sync at all although it connected to peers. need to figure out why but havent had much free time recently
bitcoin seeder
.
didnt sync at all although it connected to peers. need to figure out why but havent had much free time recently
How's it going? 
Ok thanks Tech. Connected Up. Now to wait for it to start syncing
Thank your help.
Ok thanks Tech. Connected Up. Now to wait for it to start syncing
Jump to: