pineapples
Legendary
Offline
Activity: 1204
Merit: 1000
to your stations, man the pineapples!!!
|
|
November 16, 2015, 02:49:39 AM |
|
i've imported a key into a fully synced wallet and it's reporting 0 balance. repairwallet didnt help
does -reindex or -rescan work ? or should i just try again from scratch :p
Were you able to get this resolved? i wiped the whole shebang, imported the privkey at a very low height and then let it sync. that was how i managed to do it. now i'm getting a "segmentation fault" from the daemon, and am wondering if i need to wipe it all again :/ -=-=-=- on startup i get this from the debug.log .. (with info before and after but this seems to be noteworthy-- is it my trustkey it refers to? ===== Hardened Checkpoint 0000000001837b64719a Height = 342251 ===== Hardened Checkpoint 000000000161348c7cf5 Height = 342293 ===== Hardened Checkpoint 0000000003e79221df06 Height = 342334 ===== Hardened Checkpoint 00000000011d60939d2d Height = 342385 ===== Hardened Checkpoint 0000000002fddfa9fc1f Height = 342422 ===== Hardened Checkpoint d232bcbc4a594c9d14b5 Height = 342462 ===== Hardened Checkpoint cf015fd9deddb92d3390 Height = 342517 ===== Hardened Checkpoint eccd796636d0f0918b67 Height = 342559 ERROR: CTrustKey::Expired() : Block Age Beyond Expiration Time. CTrustKey(Hash = a7a6c366088268aa53bdd0f07d8e340b07f1e6bf8cf427a4bb50c5f7d7b9808974c50d6c8cd76afc376a065ae62b38e9f54ff231caeb1113185b7fe3744c7336, Key = 215da86cd5ebef571307d651f161109260d9ab66478ff6866ff871ed152a38b9d93b49ca12282002c97f89e9704b4f3bc1b15888c775ef51531f6ef158cad5ebb8daa236030704fc, Genesis = 012a04685de66d2b58a9812931c639b819a0d07baa5196e16f40fc7decd1c3eff11310d0d2a588dcc525e8f9cfb46997afb24c1ca32ecf5082bf9556f5911bcec5ca6fbd00bf0f6ba52450909a079ff3da9d440085d790eed9cca803c419ca1f7652402e816ebf02b8365942ece677ef259d21dfde229e2a79694ea82f94439f, Tx = b3d4241986bd6e72e58a1420ae645ff8ac8e70f86d4578a00ea25ccd30c1dc2dbac4fb54728378e5dcea98b8f8701ac2e7bf7fd442b4cefa498c85e6a4804179, Time = 1438369201, Age = 9273095, BlockAge = 9273095, Expired = TRUE) CTrustPool::accept() : New Genesis Coinstake Transaction From Block 342616 CTrustPool::ACCEPTED 215da86cd5ebef571307 ERROR: CTrustKey::Expired() : Block Age Beyond Expiration Time. CTrustKey(Hash = 8fc57bb4d357508236504b8b5bae261bfd2659e50ef332601e31d6a55c7d301630e4671291aa49cd59345ad16bc136e747eba846f3740c94a1f3f5e56f5ae7ed, Key = bc130e1baf7e146beaea80764d1e10c8d57de55767cf7bfdb06145131cd00b2c776e6939f09ddadefe50c190cf988076fac5a8f403e9cf1e6469fb6f0e25bb684ba323090201ff9f, Genesis = 00a56804361743f0b42b917e8aca93a7555a5dee46e6c609ab21dc389896678d82882ae9d884cf74b39a8ebbdafc550fc758d00f13c2a391bf065aa33f08614b36d491e00da5e90f7e9a5342004b5a261c8298271840c2a39c00e112f2c24bb356b341e622ab6caf0fd4c48ec94a3d11ed44303e7085217b40d42c1a95e91a26, Tx = 392593b2be7d8655d4e67c6fd62d119f998262696b1c54c1eb94f2349c0723164be1e0a41a66ce1e11d97170201a170f880e0f24088c8af8b1d1a08dd918b0af, Time = 1438369210, Age = 9273086, BlockAge = 9273086, Expired = TRUE)
|
|
|
|
merc84
|
|
November 16, 2015, 03:13:24 AM |
|
Choosing 3 days for expiration, rather than 21. It's a balance of security and also usability. Anyone disagree?
Thank You, Viz.
How about 7 days? I have had issues with phone line where it took 7-12 days for a tech to come and fix the issue.
|
|
|
|
mumus
|
|
November 16, 2015, 06:33:49 AM |
|
Choosing 3 days for expiration, rather than 21. It's a balance of security and also usability. Anyone disagree?
Thank You, Viz.
How about 7 days? I have had issues with phone line where it took 7-12 days for a tech to come and fix the issue. I also think that 3 days is too short. I use to have 3 wallets online and about 2 weeks ago I found all of them on a forked chain. Until I realized and fixed them by re-syncing all of them at lease 3 days have passed. Of course I lost all my trust keys. Syncing the whole block chain is still painfully slow. Now I'm saving a periodic bootstrap both for linux and windows version of the wallet. (
|
|
|
|
macorcina
|
|
November 16, 2015, 08:28:00 AM |
|
What is advantage of short period, and what is disadvantage with long period. ? why Viz, force for short period, 1 day-3 day ?
It's tons of reasons to be more than 3 weeks. Technical problems, vacations, etc...
Only if Viz wants from users to baby-sitter wallets. ...then is best 4 hour..... or less if you have more wallets it's better security ? then focus on more users and more stimulations for users.
|
|
|
|
merc84
|
|
November 16, 2015, 08:46:39 AM |
|
Choosing 3 days for expiration, rather than 21. It's a balance of security and also usability. Anyone disagree?
Thank You, Viz.
How about 7 days? I have had issues with phone line where it took 7-12 days for a tech to come and fix the issue. I also think that 3 days is too short. I use to have 3 wallets online and about 2 weeks ago I found all of them on a forked chain. Until I realized and fixed them by re-syncing all of them at lease 3 days have passed. Of course I lost all my trust keys. Syncing the whole block chain is still painfully slow. Now I'm saving a periodic bootstrap both for linux and windows version of the wallet. ( I was lucky that i had a backup from when nPoS kicked off (it would also help if we had say a monthly bootstrap for eg. on the nexus.io site or linked in OP) even then it took a few hours to resync chain and when i did i had issue with wallet balance being 0. Sure i fixed the problem within 12hours but that was without community input in which case some less tech savy ppl might need a bit longer. 7 days seems much more reasonable balance between security usability, however i can see certain circumstances that would warrant a 14 day expiry. Perhaps it is possible to say freeze interest rate after 3 days and reset it after 7-14 days? Also it might be nice to have a warning popup regarding trust key expiry?
|
|
|
|
Namsbreh
|
|
November 16, 2015, 10:10:15 AM |
|
3 days is too short.
|
|
|
|
macorcina
|
|
November 16, 2015, 11:17:53 AM |
|
Some time ago, we all discuss about this, and make agreement about 21 day. And now again, same discussion from scratch. We will wait for Alzheimer to make proposal.
|
|
|
|
AliMan
|
|
November 16, 2015, 04:06:48 PM |
|
It doesn't take more than 1 day to resync a wallet from scratch, we have 3 days.
That's all how I can see it.
|
|
|
|
Conqueror
Legendary
Offline
Activity: 1354
Merit: 1020
I was diagnosed with brain parasite
|
|
November 16, 2015, 04:07:57 PM |
|
Some time ago, we all discuss about this, and make agreement about 21 day. And now again, same discussion from scratch. We will wait for Alzheimer to make proposal. I was staking one month in a row. Than I hurry up to work, not launching wallet in the morning. Than I came late evening home and surprise! 0.5 I was not opening wallet since that time. 1 day is stupidly short.
|
|
|
|
macorcina
|
|
November 16, 2015, 06:08:58 PM |
|
It doesn't take more than 1 day to resync a wallet from scratch, we have 3 days.
That's all how I can see it.
fuck you idiot baby-sitter POS. ..... feed your wallet with attention every 4 hour You must check every 4 hours, and leave all other things in life when is the problem.
|
|
|
|
tokyopotato
Legendary
Offline
Activity: 812
Merit: 1000
|
|
November 16, 2015, 10:49:44 PM |
|
Some time ago, we all discuss about this, and make agreement about 21 day. And now again, same discussion from scratch. We will wait for Alzheimer to make proposal. The issue is security, after analyzing the options, we realized that in order to encourage trust-nodes and staking for network security we should reduce the 21 day expiration to something more reasonable. We want full-nodes operating and want to reward them, however, we also don't want people jumping on and off the network every few days. 7 days seems like a good balance. Making progress on wallet and GPU miner. Still on target for Nov 25th. The team is certainly making progress in terms of developing consensus around core ideas and philosophy of Nexus.. hope to share our vision more intricately soon. Cheers
|
|
|
|
macorcina
|
|
November 16, 2015, 11:52:45 PM Last edit: November 17, 2015, 12:20:03 AM by macorcina |
|
Some time ago, we all discuss about this, and make agreement about 21 day. And now again, same discussion from scratch. We will wait for Alzheimer to make proposal. The issue is security, after analyzing the options, we realized that in order to encourage trust-nodes and staking for network security we should reduce the 21 day expiration to something more reasonable. We want full-nodes operating and want to reward them, however, we also don't want people jumping on and off the network every few days. 7 days seems like a good balance. Making progress on wallet and GPU miner. Still on target for Nov 25th. The team is certainly making progress in terms of developing consensus around core ideas and philosophy of Nexus.. hope to share our vision more intricately soon. Cheers what is difference in 7 and 21 day. What is secure 7 day and 21 day is not secure ? if you start the wallet after few hours it come genesis block. after 24 hour inactivity, when you start wallet again , after few hour is come another genesis block. why is that more secure, than something else. At this moment i have more reward to start wallet every 25 hour, and more genesis reward, then trust reward. i don't see logic in all this. what you want to achieve with this whole concept. ? At this moment this looking like POS reward for rich wallets with milions , and punish for someone with for exemple with 10000 coins. If is more secure to run more wallets then you stimulate small wallets, not big one. For example, genesis only for exactly 10 000 coins. for more then 10 000 is no reward. and reward base for 10 000 coins. Whit this attract 500 people, for exemple to staking 500 x 10 000 coins. 5 mil coins staking. this is 500 nodes. This is secure , right ? Much more than 20 - 50 nodes. if someone want to earn with staking, then you stimulate users to run more wallets. this is good for network, marketing, and this expand user base. And spread distributions, and less coins is on exchange. And pice go up.
|
|
|
|
merc84
|
|
November 17, 2015, 02:52:18 AM |
|
Some time ago, we all discuss about this, and make agreement about 21 day. And now again, same discussion from scratch. We will wait for Alzheimer to make proposal. The issue is security, after analyzing the options, we realized that in order to encourage trust-nodes and staking for network security we should reduce the 21 day expiration to something more reasonable. We want full-nodes operating and want to reward them, however, we also don't want people jumping on and off the network every few days. 7 days seems like a good balance. Making progress on wallet and GPU miner. Still on target for Nov 25th. The team is certainly making progress in terms of developing consensus around core ideas and philosophy of Nexus.. hope to share our vision more intricately soon. Cheers How about rewarding users who stake more frequently with a faster ramp up of interest rate? So for example if the expiry is 7 days users who stake daily would have their interest rate ramp up faster than someone who only staked weekly.
|
|
|
|
AliMan
|
|
November 17, 2015, 04:23:48 AM |
|
It doesn't take more than 1 day to resync a wallet from scratch, we have 3 days.
That's all how I can see it.
fuck you idiot You'll definitely never 'Conqueror' with that attitude.
|
|
|
|
Videlicet
Legendary
Offline
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
|
|
November 17, 2015, 06:43:16 AM Last edit: November 17, 2015, 07:03:18 AM by Videlicet |
|
Yeah it is way too short, what I've been thinking is actually having the trust key expire after the trust is lost, so if you have more trust, your key will be able to be held longer without blocks rather than a fixed day. An example could be your key has been active for 1 month, it expires in 3 days, active for 3 months expires in 9 days, 6 months, 18 days, so forth. What do you guys think? Thank You,Viz.The reason this has been ongoing is because I haven't settled on a satisfactory solution until now regarding balancing security and usability. So with this new proposal those with more trust will have more time they can wait before their key expires with not staking, but on the other hand, you lose trust and interest for not staking, but not down to 0.5, just down to the levels of trust in your key. So keeping a key offline will slowly degrade its trust until it becomes expired. This means that more trust == more time before expiration, almost like a reverse process of building trust that comes when you stake, where you lose trust when you don't stake from the levels of trust you already have established.Last note, how about a trust key reactivation on new update which means, your node will be able to use an expired key that was created before update time lock if you produce a block within 24 hours of the new update. This can revive your lost trust keys, especially the ones that had higher interest rates if you stake with a 2.0.1 node. Sound Good?
|
[ Nexus] Created by Viz. [ Videlicet] : "videre licet - it may be seen; evidently; clearly"
|
|
|
macorcina
|
|
November 17, 2015, 07:09:04 AM |
|
How correlate security with number of staking walllets ?
For exemple if you have 50 staking walets with key, and 500 with key.
More staking wallets more security ? Yes or no ? and point is to reward runing wallets 24hour, ? yes or no. ? if its this, then make reward to run wallets, not reward for rich people.
this is 2 different things .
|
|
|
|
Videlicet
Legendary
Offline
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
|
|
November 17, 2015, 07:13:40 AM |
|
No, more staking wallets on one key is less security. That's why I have a minimum interval with all trust keys set to 5 right now which means your trust key can only produce a trust block every 5 network blocks. Will probably increase this number with the new update to try and limit stake blocks to around 1 - 2 a day. Will still give you the same income, just less blocks which will ensure you can't attempt a block streak of producing too many blocks in a row to try and double spend.
Thank You, Viz.
|
[ Nexus] Created by Viz. [ Videlicet] : "videre licet - it may be seen; evidently; clearly"
|
|
|
macorcina
|
|
November 17, 2015, 07:22:30 AM |
|
we have 2 goal. 1 is interest 2 is reward running wallet for security if you need more wallets for network security then solve this separately, and fix big reward for 10000 coins for running wallet 24 hour. rest of coins in wallet reward for interest.
|
|
|
|
Videlicet
Legendary
Offline
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
|
|
November 17, 2015, 07:31:30 AM |
|
How about also features in the wallet being unlocked if you have trust, such as casinos, chats, whatever you can imagine. The trust network can provide a lot more than just interest rates... The interest rates now are just the beginning, the sky is the limit here.
Thank You, Viz.
Note: I like to work around coin holdings as much as possible because there are some users in certain countries that have a hard time even accumulating 1000 Niro...
|
[ Nexus] Created by Viz. [ Videlicet] : "videre licet - it may be seen; evidently; clearly"
|
|
|
tokyopotato
Legendary
Offline
Activity: 812
Merit: 1000
|
|
November 17, 2015, 07:49:06 AM Last edit: November 17, 2015, 08:09:39 AM by tokyopotato |
|
I kind of like what macorcina is saying here. If you have a trust key, you are rewarded a static amount per block, and then holdings staked are rewarded on a dynamic % basis.
I think we are going to go with dynamic trust expiration. For every 7 days producing blocks (wallet staking), you get 1 day grace period before expiration. So after 28 days, you would have 4 days grace period before expiration. For every 7 months, 1 month grace period before expiration. So a proportion of 7/1.
Here's some other ideas we are floating right now. Trust keys enabling advanced features such as domain/name registry.
We are looking to expand the "time is money" concept, and using time to add valuable features. Those with trust would be able to unlock more features in the protocol such as domain/name registry on the blockchain.
|
|
|
|
|