|
Added a few more coins to the Faucet
|
|
|
|
I would like to quietly point out that in the last few moments I GOT MY STAKE!Many thanks for your efforts in drilling into the logic here and while i was typing I GOT MORE STAKE! Your theory was bang on sir! Excellent!  Hope Tranz reads this. I would love to hear is take on this  |
|
|
|
EDIT: @PressF1, do you know how old were your blocks when they staked?
Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:
Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.
so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.
One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.
I was asking in order to support my theory, were you about at 30 days of age, or more ? Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur. I guess the only other thing that needs confirming (I think I have seen this on the explorers already) Is that stakes that should be receiving more than the cap are being pegged back to 1k and not ignored or rejected obviously my blocks would have got significantly more than 1k but I am expecting 1k exactly per block I've had a 5k block of exactly 46 day old, got 1000 CAP on the 4th. if there was no cap, I would of seen 1260 CAP. if it had a bug, I wouldn' t have seen anything. so I can confirm everything runs smooth. There is just this mid min/max range threshold before staking that bugs me |
|
|
|
EDIT: @PressF1, do you know how old were your blocks when they staked?
Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:
Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.
so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.
One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.
I was asking in order to support my theory, were you about at 30 days of age, or more ? Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur. Ok thanks, it's good to know. so far it looks like what I observed on GrowthCoin, no stake was generated under 9 days there. I'll keep an eye on the 33 days minimum. So I guess if flungspun doesn't get his stake around 6pm tonight... then the next target to look for would be around 33 days. It would be good to know if anyone can report a stake before 30 days (or near the minimum age) |
|
|
|
EDIT: @PressF1, do you know how old were your blocks when they staked?
Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:
Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.
so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.
One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.
I was asking in order to support my theory, were you about at 30 days of age, or more ? |
|
|
|
MY wallet doesn't seem to be staking either. I haven't had it open 24/7 but I have high coin weight and have kept it open for several hours at a time. Will try troulbe shooting it soon.
Same here. My coin weight is 171447 and ive had my computer on for 2 days. what's the exact date of each block you have ready for stake? Non staking blocks. There is also a tiddler of 0.998 which I moved to another address. Status: 42845 confirmations
Date: 06-Jun-14 18:00
From: unknown
To: Eqq3Ed9UEDLEa16Jg8degVV3ESFWvnK9pA
Credit: 10000.00 CAP
Net amount: +10000.00 CAP
Transaction ID: e6c8b0075d341008fe35da80213e7ff7068178ea382632b60ac70dc640275d2f
Status: 42822 confirmations
Date: 06-Jun-14 18:10
From: unknown
To: Eqq3Ed9UEDLEa16Jg8degVV3ESFWvnK9pA
Credit: 10000.00 CAP
Net amount: +10000.00 CAP
Transaction ID: 62aa70d5add1333ddd42a0bb7f91c77ee94206958616376dadf6730cb2c7521c
Status: 42807 confirmations
Date: 06-Jun-14 18:25
From: unknown
To: Eqq3Ed9UEDLEa16Jg8degVV3ESFWvnK9pA
Credit: 10000.00 CAP
Net amount: +10000.00 CAP
Transaction ID: 824c3d78fa5bb62817590d967eeb6b012c0398ff7128030e059cee6e3d14cdbd
Status: 42804 confirmations
Date: 06-Jun-14 18:29
From: unknown
To: Eqq3Ed9UEDLEa16Jg8degVV3ESFWvnK9pA
Credit: 10000.00 CAP
Net amount: +10000.00 CAP
Transaction ID: 0244f1ab01d6d5762abe962fd5b10fdb7c47cceb6697410fe9c6bb53e064dbd3 The first one is obviously the devils block 6/6 @18:00 I just noticed this. It seems that you blocks are old enough, but I wonder if this is not the same thing I experience with GrowthCoin. min/max age is 15/45 days. so I guess you should get your stake anytime soon (arround midway between min and max age) so likely today you should get your stake. With growthcoin, the stakes always seems to come in at around 9 days of age (witch is middle point between min and max age). For the record, I got my stakes already, but my blocks were from May, I know Tranz's were too. So likely, those that already had their stakes, were from May too! You could also be out of luck (but I doubt it this is what we are seeing) Lastly, and this goes for all. Make sure you run version 2.1. It has a patch for staking larger blocks. Let us (me) know if you get your stake today or tomorrow Well still no luck yet. guess we will have to wait and see. I'm used to big HBN blocks staking almost immediately. Been doing 100s of little ones recently though - feel a block combining session coming on Yeah, I know HBN stakes relatively close to the min stake age. Your first transaction was at 18:00, so it's about 4 hours from now right? (or is that your local time) in any case, I'd bet you will stake close after that time. That would be the best scenario, worst case you'd have to wait another 15 days ! EDIT: @PressF1, do you know how old were your blocks when they staked? |
|
|
|
MY wallet doesn't seem to be staking either. I haven't had it open 24/7 but I have high coin weight and have kept it open for several hours at a time. Will try troulbe shooting it soon.
Same here. My coin weight is 171447 and ive had my computer on for 2 days. what's the exact date of each block you have ready for stake? Non staking blocks. There is also a tiddler of 0.998 which I moved to another address. Status: 42845 confirmations
Date: 06-Jun-14 18:00
From: unknown
To: Eqq3Ed9UEDLEa16Jg8degVV3ESFWvnK9pA
Credit: 10000.00 CAP
Net amount: +10000.00 CAP
Transaction ID: e6c8b0075d341008fe35da80213e7ff7068178ea382632b60ac70dc640275d2f
Status: 42822 confirmations
Date: 06-Jun-14 18:10
From: unknown
To: Eqq3Ed9UEDLEa16Jg8degVV3ESFWvnK9pA
Credit: 10000.00 CAP
Net amount: +10000.00 CAP
Transaction ID: 62aa70d5add1333ddd42a0bb7f91c77ee94206958616376dadf6730cb2c7521c
Status: 42807 confirmations
Date: 06-Jun-14 18:25
From: unknown
To: Eqq3Ed9UEDLEa16Jg8degVV3ESFWvnK9pA
Credit: 10000.00 CAP
Net amount: +10000.00 CAP
Transaction ID: 824c3d78fa5bb62817590d967eeb6b012c0398ff7128030e059cee6e3d14cdbd
Status: 42804 confirmations
Date: 06-Jun-14 18:29
From: unknown
To: Eqq3Ed9UEDLEa16Jg8degVV3ESFWvnK9pA
Credit: 10000.00 CAP
Net amount: +10000.00 CAP
Transaction ID: 0244f1ab01d6d5762abe962fd5b10fdb7c47cceb6697410fe9c6bb53e064dbd3 The first one is obviously the devils block 6/6 @18:00 I just noticed this. It seems that you blocks are old enough, but I wonder if this is not the same thing I experience with GrowthCoin. min/max age is 15/45 days. so I guess you should get your stake anytime soon (arround midway between min and max age) so likely today you should get your stake. With growthcoin, the stakes always seems to come in at around 9 days of age (witch is middle point between min and max age). For the record, I got my stakes already, but my blocks were from May, I know Tranz's were too. So likely, those that already had their stakes, were from May too! You could also be out of luck (but I doubt it this is what we are seeing) Lastly, and this goes for all. Make sure you run version 2.1. It has a patch for staking larger blocks. Let us (me) know if you get your stake today or tomorrow |
|
|
|
I haven't staked yet either despite having held coins forever now. db.log has this Lock table is out of available lock entries
and debug.log has this: 07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 ERROR: mempool transaction missing input
07/06/14 14:14:11 received block 0ac317b1ecb264b379c1
07/06/14 14:14:11 SetBestChain: new best=0ac317b1ecb264b379c1 height=527925 trust=2145786651908 date=07/06/14 14:14:07
07/06/14 14:14:11 ProcessBlock: ACCEPTED
for the db lock try this https://bitcointalk.org/index.php?topic=241445.msg7362114#msg7362114for mempool error, restart the client. we had a big rollback on the 4th and your client still holds old transactions in memory. |
|
|
|
MY wallet doesn't seem to be staking either. I haven't had it open 24/7 but I have high coin weight and have kept it open for several hours at a time. Will try troulbe shooting it soon.
Same here. My coin weight is 171447 and ive had my computer on for 2 days. what's the exact date of each block you have ready for stake? |
|
|
|
One little Coin Control bug I noticed today while cleaning up some dust. Using 2.1 version.
On ~1/3 of the sends I was doing the calculated send fee was not correct. Sometimes it was more sometimes it was less (ie coin control calculate fee to be 0.01 but upon sending it claims fee will be 0.011, another calculated fee at 0.006 but on sending it was only 0.004.)
Pretty minor bug but the underestimate causes the send to fail as your total to send becomes less than the value+fee.
I don't think it's a bug, more a lack of better solution. Coin control will give you an estimate of the fees no the actual fees. I find that the more blocks you have selected, the farther away you will be from reality. I didn't look into the code for this. But I know fees can be estimated like this tx_size = (inputs * 148) + (outputs * 34) + 10 ± "# inputs" so I guess that plus and minus inputs argument could throw off the estimation the more inputs you have selected. Maybe a better estimation equation could be used. I never found one. |
|
|
|
Posting for updates welcome to the community |
|
|
|
We've just hit a mile stone, 1 million HBN blocks have been solved and just over 5.125 million HBN generated. I think inflation has been well controlled this far. For those who just start following, there is a 5 HBN reward for block solving, if this was purely PoW, we would have 5 Millions HBN in the network, 125 thousand more is not that bad (about 2,5% more) This is cool I'm sad. I missed it.  It's like the first time hitting 100k on your car.. lol yeah, it does feel that way a little bit |
|
|
|
We've just hit a mile stone, 1 million HBN blocks have been solved and just over 5.125 million HBN generated. I think inflation has been well controlled this far. For those who just start following, there is a 5 HBN reward for block solving, if this was purely PoW, we would have 5 Millions HBN in the network, 125 thousand more is not that bad (about 2,5% more) This is cool |
|
|
|
You can actually still access it using a simple trick.
If you're using Windows, simply open up c:\windows\system32\drivers\etc\hosts file in your notepad and add the following line at the end of the file, save and you're done:
190.93.241.217 coinex.pw
In case the file cannot be saved after modification, you need to open notepad as administrator.
Anybody knows anything about the status? Owners given up or...?
Great, people who know what they're doing can access it. Now new victims won't blunder into the site and deposit funds, as has been happening for months. No more victims of Coinex, please. thanks for posting that IP i just hope that they put all the wallets back online so we can withdraw the remaining balances! It's been over 3 months for me! I'm checking a couple of times a week, without luck  |
|
|
|
The CP server being down and signing wrong blocks did mess up Crypsty most of all... Trades that occurred before the roll back screwed their accounting. I'm sure everything will be fine on their end once they audit the transactions. As far as for flound, he should be made aware of the consequences of the signing blocks when not in sync! Good job on everything Tranz, and for quickly messaging flound about this! Live and learn It looks like this was either a deliberate attack or a misbehaving peer that caused the checkpoint server to become lagged. If it was deliberate then the attacker got very lucky because the CP server is not configured to accept incoming connections. So it happened to connect out to that peer and then got inundated with getblocks request which caused the daemon to become lagged. So lagged in fact that only 2 peers were still connected by the time I logged into the server this morning. I've seen this happen with other currencies and I'm pretty sure it's some kind of attack. Just a very bad time for it to occur. I was working all day yesterday on Multipool issues with our east provider so I didn't really have time to check on it. I'm going to give Tranz control of the checkpoints so that he can monitor things more closely. For now the server is turned off. Thanks for the update, It looks like everything is back to normal |
|
|
|
The CP server being down and signing wrong blocks did mess up Crypsty most of all... Trades that occurred before the roll back screwed their accounting. I'm sure everything will be fine on their end once they audit the transactions. As far as for flound, he should be made aware of the consequences of the signing blocks when not in sync! Good job on everything Tranz, and for quickly messaging flound about this! Live and learn |
|
|
|
mac wallet perchance? now i'm investing in this, i'd like to have my coins on my main pooter  Yes I was going to ask Unick to make one, just as soon as the fork is complete. So just in case there are some code changes, I won't have to bug him twice. fabulous, thanks! I already have a working build from the latest commits. I must warn you, I never found why the build sometimes failed on some Macs... So it might work or not for you. but you can have a try http://cap.blockx.info/bottlecaps-2.1.0.0-macosx.dmgonly 8 hours left before the fork !!! |
|
|
|
Stupid question that I should know the answer to, but I don't have a whole lot of experience with the daemon... on getinfo is "stake" telling me how many coins have weight?
Not a stupid question, we are all learning things on this journey the "stake" tells you how many coins are currently unavailable due to currently being staking. It's the same "stake" as on the overview tab in the Qt client |
|
|
|
Actually in PC I have 0 or 1 connection. in the log I have (relative to my pool node): received block 3a63fb53ec6d9cf5b0d2
Misbehaving: 188.226.155.94:17177 (0 -> 100) DISCONNECTING
disconnecting node 188.226.155.94:17177
ERROR: ProcessBlock() : block with too little proof-of-stake
if I look at other nodes, I have something like this (xxxxx=masked of sensible data, MYIP=my ip address): trying connection 66.227.210.205:17177 lastseen=3.3hrs
connection timeout
trying connection 112.5.237.72:17177 lastseen=33.3hrs
IRC :irc.shakeababy.net 439 * :Please wait while we process your connection.
IRC :irc.shakeababy.net NOTICE AUTH :*** Looking up your hostname...
IRC :irc.shakeababy.net NOTICE AUTH :*** Checking Ident
IRC :irc.shakeababy.net NOTICE AUTH :*** No Ident response
IRC :irc.shakeababy.net NOTICE AUTH :*** Your forward and reverse DNS do not match, ignoring hostname.
IRC SENDING: NICK xxxxxxxxxxxxxx
IRC SENDING: USER xxxxxxxxxxx 8 * : xxxxxxxxx
IRC :irc.shakeababy.net NOTICE xxxxxxxxxx :*** Banned Temporary K-line 4320 min. - [G][netsec] [xxxxxxx!~xxxxxx@MYIP: xxxxxxxxxxxx] has been matched to a known bot pattern r#393 (Bitcoin Clients - http://s.rizon.net/peercoin) - Visit http://abuse.rizon.net/akills/lookup?ip=MYIP&drone for more information. (Akill ID: xxxxxxxxx) (2014/6/22 19.10)
connection timeout
trying connection 109.235.190.7:17177 lastseen=4.7hrs
connection timeout
trying connection 201.209.45.121:17177 lastseen=117.1hrs
connection timeout
trying connection 85.169.43.123:17177 lastseen=5.5hrs
connection timeout
trying connection 75.152.12.122:17177 lastseen=4.9hrs
IRC ERROR :Closing Link: MYIP (Rejected)
socket closed
This is strange for me: why the wallet make a IRC connection? I suspect that even if I activate minting when all is cynched, it took 100% of processor for making POS calculation that it lost cycncronization after some hours and so local copy goes in fork again. Try pulling the latest version from github, I have disabled IRC by default. you can try to delete your peers.dat file too. |
|
|
|
is there any plan for this coin? unick,you are the monitor of the development of grw. As far as I'm concerned, - Make a Better wallet
- Have a stable network and hash rate
- Have a higher/more stable trading price and volume
- Get listed on coinmarketcap.com, coinwarz and others like it
- Have more exchanges where to trade the coin
Of course this is not MY coin but OUR coin, I am happy to contribute in any ways I can, and I will. I would love to see more people joining forces and contributing in their own ways. Having businesses using this coin could be good for the coin. I have sent 15k for bounties to the development address... what about a 1k GRW bounty for every merchant we can get. What do you guys think about that? |
|
|
|
|
Show Posts
