Pretty great.
So If I hold 5000 coins for 30 days, how big will the PoS be?
PoS reward is 0.05 coins per CoinYear, so if you stake 5000 coins with age of 30 days, it yields 150`000 CoinDays, which is ~410.96 CoinYears. 410.96 * 0.05 = ~20.55 coins. So the formula is: interest = (BALANCE - RESERVED_BALANCE) * DAYS_HELD / 365 * 0.05
You can choose to reserve some of your balance and not stake it (because it's unspendable for quite a long time when you stake it) and DAYS_HELD can be between 30 and 90 days. EDIT: the actual formula in the source is a bit different, but this is a pretty close approximation. |
|
|
|
Looks like the network hashrate is steady at 40Mhash. Anyone happen to know when the POS blocks are due to pop up in the wallets?
soon™ |
|
|
|
Is anyone willing to work with me to create a altcoin-creating GUI program?
You just enter a couple of parameters, a logo, and an abbreviation and it will generate the source for you?
You forgot the "premine" checkbox.  |
|
|
|
Is this really CPU mining rather than GPU mining? How do you ensure that the GPU owners are not ahead of the rest of us?
Not many people have GPU miner yet, and GPUs will probably stop working alltogether in August. http://yacexplorer.tk/graphs.htm#techlet me send you a little .01 YAC Okay it seems that wallet works. However, I stop receiving any money recently since 45 minutes ago. I wonder why. sent some back, is it working? you need to have unlocked wallet if you're solo-mining, else you won't recieve anything |
|
|
|
1. Why would someone ever switch to 1440 blocks shown on a single page? It is pointless since there will hardly ever be exactly 1440 blocks solved in one day.
2. Cool, but it is on graphs page, not main page so anyone checking just block, address or transaction will never see it.
1) meh 2) why would they want to? imo anyone interested in details will browse through the technical info and find the links there |
|
|
|
Is this really CPU mining rather than GPU mining? How do you ensure that the GPU owners are not ahead of the rest of us?
Not many people have GPU miner yet, and GPUs will probably stop working alltogether in August. http://yacexplorer.tk/graphs.htm#tech |
|
|
|
Two suggestions:
1. Remove showing 2016 blocks (count=2016) since it has no connection with YAC, it is made for cryptocoins that retarget every 2016 blocks.
2. Put link for this thread somewhere on explorer webpages.
Done. You replaced 2016 with 1440 (in what sense is that value relevant to YAC?) and there is no link pointing to this thread.  1) 1 day / 60 second blocks = 1440 blocks/day 2) at the end of technical info http://yacexplorer.tk/graphs.htm#tech |
|
|
|
Server up again, let's see for how long it will last this time...
EDIT: Gah, it went down again... -.-" However, I found out that this is a known problem in Abe related to concurrent blockchain processing when new block is received from the network (race condition or something). I've implemented a quick fix - using a separate process for writing new blocks into DB once in a while (so webpage might be delayed by up to 60 seconds, not a big deal). Hopefully this avoids another DB corruption until proper fix is implemented in Abe.
Ahh, my young ABE Padawan. The first step in your quest for a smooth running explorer is to switch to the FastCGI server and stop using the default built in python server. You have the right idea about separate processes for update verses serve. Keep two copies of abe.py with different names like abe.py and uabe.py. Any requests from the web server will use one abe.py with a conf file that uses a empty bracket for datadir (datadir = [] ). This will stop web requests from tripping an update. To update the server use the blocknotify option in the coin daemon conf file and point it to a script that will run the second abe.py (uabe.py) with a full conf file to trigger a database update. The reason for the two named abe.py has to do with FastCGI sticking its big nose into your database update process if it has the same name as the process it trips. If you need any more help, just let me know.  I already solved it, but thanks anyway. |
|
|
|
Two suggestions:
1. Remove showing 2016 blocks (count=2016) since it has no connection with YAC, it is made for cryptocoins that retarget every 2016 blocks.
2. Put link for this thread somewhere on explorer webpages.
Done. |
|
|
|
Random Yacoin Facts: - There are 30616 addresses used so far.
- Top 10 receiving addresses:
address received
YBJeQQFCipbC4LrZTnTu6j5rSAMsqRkGJb 441151.00000000
Y8pzvdVPNKjhRQYnRWGd1sEcE7WKrGpqcV 314843.88000000
YDFcVs8sxTbym6K6msd2ziXtp8kwYhG1rw 304656.25000000
YJH8f3XKtTXWHpCAgYpQCi5HAQ7SCPGSXA 273753.93000000
Y2e1VP9ZpwYCbVMk7RRhGDLwRKyuQwjzGQ 186557.13978700
Y42xBGnxyoNfHDfvGiVfH8D8U34xthPxy8 159695.18000000
YAP2R5EfeiBSREwUJmdKEzd5HhvmpfkLHs 142114.29000000
Y5M9ec642cQGfe35HyYwqgNxvKr4ufoWiT 110849.44126400
Y9A8mdy2rqFihhGssGZEc7Npg5YZU4byHX 102909.92500000
YNwKaaULjo2hPJCi4FzVvqLonykLAq6SPT 102909.56990000
- Top 10 sending addresses:
address sent
YDFcVs8sxTbym6K6msd2ziXtp8kwYhG1rw 304656.25000000
YAP2R5EfeiBSREwUJmdKEzd5HhvmpfkLHs 142114.29000000
Y5M9ec642cQGfe35HyYwqgNxvKr4ufoWiT 110849.44126400
YNwKaaULjo2hPJCi4FzVvqLonykLAq6SPT 102909.56990000
Y5JxizRK44ahePgNqgZDRjE9Bks58NohWQ 90320.46000000
Y5ve8DUxxUsX2uwcw54Mpwp4zV1gTeB56y 82832.35000000
YB24c3Uwenem72g7dhY5aP2RJg8oY72pzL 82732.00000000
Y1UdvTxdfMrCckK8S4ceS7VxR3ivx7yWMq 76614.71400000
YF3gMrRKbgL3kkNwG42XnBzjk23wvgWi7W 74413.44000000
Y7YMAVrC6YYe28kgqEog9e2LbjU5iTHhsm 67241.13272900
- Top 10 addresses by final balance:
address balance
YBJeQQFCipbC4LrZTnTu6j5rSAMsqRkGJb 441131.00000000
Y8pzvdVPNKjhRQYnRWGd1sEcE7WKrGpqcV 314843.88000000
YJH8f3XKtTXWHpCAgYpQCi5HAQ7SCPGSXA 273741.93000000
Y2e1VP9ZpwYCbVMk7RRhGDLwRKyuQwjzGQ 185299.17978700
Y42xBGnxyoNfHDfvGiVfH8D8U34xthPxy8 99431.00000000
Y9kxx3oWXnVGV5gd8yHUMWcmV3BFRaLQAX 91402.91000000
Y4D4gQ32YhGP61CTRHJG9HM9M8HRAxMHom 74280.00000000
YMbVUEiaTEKM5wvQFtQ9cM9fNUMYceiVYA 70000.00000000
Y9A8mdy2rqFihhGssGZEc7Npg5YZU4byHX 52910.14500000
Y1dncJeBobRiYiBop6LWsUXq9fm8HbQfsp 50853.56924000
|
|
|
|
Rise Nfactor RISE !
Here comes 3x longer confirmation time  |
|
|
|
If you are doing solo mining and have to leave it unencrypted, I suggest making two wallets and transfer coins to the encrypted wallet from time to time. As always, backup your data before running any random downloads from teh interwebs.
Sorry if this is offtopic but can't I solo-mine with my wallet encrypted? My wallet is encrypted and I'm solo-mining with the minerd and I'm not getting any errors.. You won't find any block if you have your wallet encrypted and locked. Either unlock it for a long time period (walletpassphrase <pass> 99999999) or remove encryption. |
|
|
|
You need a formula for the block reward, Nfactor affects only difficulty. EDIT: from the source: int64 GetProofOfWorkReward(unsigned int nBits)
{
CBigNum bnSubsidyLimit = MAX_MINT_PROOF_OF_WORK;
CBigNum bnTarget;
bnTarget.SetCompact(nBits);
CBigNum bnTargetLimit = bnProofOfWorkLimit;
bnTargetLimit.SetCompact(bnTargetLimit.GetCompact());
// ppcoin: subsidy is cut in half every 64x multiply of difficulty
// A reasonably continuous curve is used to avoid shock to market
// (nSubsidyLimit / nSubsidy) ** 6 == bnProofOfWorkLimit / bnTarget
//
// Human readable form:
//
// nSubsidy = 100 / (diff ^ 1/6)
CBigNum bnLowerBound = CENT;
CBigNum bnUpperBound = bnSubsidyLimit;
while (bnLowerBound + CENT <= bnUpperBound)
{
CBigNum bnMidValue = (bnLowerBound + bnUpperBound) / 2;
if (fDebug && GetBoolArg("-printcreation"))
printf("GetProofOfWorkReward() : lower=%"PRI64d" upper=%"PRI64d" mid=%"PRI64d"\n", bnLowerBound.getuint64(), bnUpperBound.getuint64(), bnMidValue.getuint64());
if (bnMidValue * bnMidValue * bnMidValue * bnMidValue * bnMidValue * bnMidValue * bnTargetLimit > bnSubsidyLimit * bnSubsidyLimit * bnSubsidyLimit * bnSubsidyLimit * bnSubsidyLimit * bnSubsidyLimit * bnTarget)
bnUpperBound = bnMidValue;
else
bnLowerBound = bnMidValue;
}
int64 nSubsidy = bnUpperBound.getuint64();
nSubsidy = (nSubsidy / CENT) * CENT;
if (fDebug && GetBoolArg("-printcreation"))
printf("GetProofOfWorkReward() : create=%s nBits=0x%08x nSubsidy=%"PRI64d"\n", FormatMoney(nSubsidy).c_str(), nBits, nSubsidy);
return min(nSubsidy, MAX_MINT_PROOF_OF_WORK);
}
|
|
|
|
I've noticed a huge increase in network hashrate. It is now 600x my own hashrate, while it was still 300x two days ago.
The client sometimes reports garbage, take a look at these graphs, they're averaged over 144 blocks (10 blocks for 24h graphs). Network hashrate actually decreased on the 29th due to the Nfactor change. http://yacexplorer.tk/graphs.htm |
|
|
|
|
Show Posts
