All Activity
This stream auto-updates
- Past hour
-
tien kim changed their profile photo
-
nguoi ngu changed their profile photo
-
ten ho changed their profile photo
- Today
-
rahul boom changed their profile photo
-
Aso Hacker joined the community
-
Laleh Sadeghi joined the community
-
Xaya-Gaming.net Main Site Launch *BACK ONLINE* | *Liquid.com Trade Data* + *Blockreward Info* added
DarkClaw replied to casp0or's topic in General
Yes, exactly. I already have hourly (~120 blocks) and daily (~2880 blocks) hashrates estimated elsewhere, so it makes little sense for me to also calculate that at each individual block. I think it is all correct now then. Also, do you have any explanation for why there is actually ~31.5 s per block rather than the targeted 30 s? It works out so there are about 135 fewer blocks per day than expected. -
Samsung Nokia changed their profile photo
-
vasiliylitvin joined the community
-
علي احمد الباكري changed their profile photo
-
Бектеналы Бердалиев changed their profile photo
-
Äjîbådë Blëssîng Ãyøbåmï changed their profile photo
-
mahmood naj joined the community
-
Daniel León changed their profile photo
-
Xaya-Gaming.net Main Site Launch *BACK ONLINE* | *Liquid.com Trade Data* + *Blockreward Info* added
domob replied to casp0or's topic in General
If I see it correctly, your method works off the current difficulty only. The method used in the RPC actually calculates the hash rate over a previous period of time, based on the individual difficulty values of the blocks (e.g., it handles changes of the difficulty over time). There is no particular reason why I did it that way, except that this is also how upstream Bitcoin works - except that I had to extend the logic to handle multi-algo correctly. -
Trần Minh Trường changed their profile photo
- Yesterday
-
Xaya-Gaming.net Main Site Launch *BACK ONLINE* | *Liquid.com Trade Data* + *Blockreward Info* added
DarkClaw replied to casp0or's topic in General
Ok, should be better now. I am not calculating it the exact same way as the RPC, which averages the work over the last 120 blocks by default (see GetNetworkHashPS and getnetworkhashps in the source). Instead I am doing: # https://en.bitcoin.it/wiki/Difficulty # Hashrate for difficulty 1 at one block per minute (MHash/s) # hr1 = 1e-6*(2^32)/60 hr1 = 71.58279 # ... # For all blocks starting at 440k, multiply neo hashrate by 1.5 and sha by 0.5 # Originally blocks were 50-50 but now are 75-25 (75/50 = 1.5, 25/50 = 0.5) flag_frk = height >= 440e3 hr_adjust = rep(1, nBlocks) hr_adjust[idx_neo & flag_frk] = 1.5 hr_adjust[idx_sha & flag_frk] = 0.5 HR_target = diff*hr1*hr_adjust So the results won't be exactly the same, but I don't see why domob did it the more complicated way. Do you have any comments @domob? For example, here is that same block from earlier: date height thisHash prevHash isOrphan version size algo diff nTx HR_target blocktime_sha blocktime_neo blocktime_all 2019-01-15 11:06:55 510551 a6b3c246fa132570dc73cab33a02d85fe83c84995606a517439c16f61decac0c c7962b5849ec277cd1d7de3e90bdb88f1db66e84b1d4dacf5a0dec0266cae917 FALSE 536870912 350 Neoscrypt 0.618021501320256 1 66.359555016739 NA 0.483333333333333 0.483333333333333 -
if it works perfectly, thank you very much
-
The solution is to change the default program for VBS files. On that file, right-click and choose Properties. On the "Opens with:" line, click Change... Choose "Microsoft ® Windows Based Script Host" and click OK. If you need to browse, the file location is: C:\Windows\System32\wscript.exe Once you've changed that, you should be good to go.
-
when I download and execute the xaya portfolio, this error comes up: Adobe Acrobat Reader could not open "shell_mainx86.vbs" because it is not supported file type or is damaged (for example, it was sent as an email attachment and not decoded correctly) if someone tells me how to fix it I would appreciate it
-
Felipe Cupido joined the community
- Last week
-
Although i did not buy coin for exchange, for some hoder/supportor, that doesn't means free. i sell out all the huc after snapshot, the only reason i keep huc is wait for transit to CHI
-
ahmad karimi joined the community
-
just @sorji the 3 CHI per HUC was based on some max supply of 1billion in the end the same "ratio" was given, otherwise huc owners would have had 90% of the coins or something on launch.. it was a free airdrop and was still quite generous tbh
-
Xaya-Gaming.net Main Site Launch *BACK ONLINE* | *Liquid.com Trade Data* + *Blockreward Info* added
DarkClaw replied to casp0or's topic in General
Here is what I have for that block: date height thisHash prevHash isOrphan version size algo diff nTx HR_target blocktime_sha blocktime_neo blocktime_all 2019-01-15 11:06:55 510551 a6b3c246fa132570dc73cab33a02d85fe83c84995606a517439c16f61decac0c c7962b5849ec277cd1d7de3e90bdb88f1db66e84b1d4dacf5a0dec0266cae917 FALSE 536870912 350 Neoscrypt 0.618021501320256 1 44.2397033444926 NA 0.483333333333333 0.483333333333333 So the difficulty matches up but not the hashrate... Here is how the hashrate is calculated: # https://en.bitcoin.it/wiki/Difficulty # Hashrate for difficulty 1 at one block per minute (MHash/s) # hr1 = 1e-6*(2^32)/60 hr1 = 71.58279 # ... HR_target = diff*hr1 So yes, looks like this is a bug for data after the hardfork, since it should be calculated for one block every 40 seconds if NeoScrypt and every 120 seconds if sha256d. Thanks, I will fix later. -
Xaya-Gaming.net Main Site Launch *BACK ONLINE* | *Liquid.com Trade Data* + *Blockreward Info* added
DarkClaw replied to casp0or's topic in General
The hashrate you see from the RPC is calculated for each block. You can see this data in the "block" tab for the charts. The data you have in the screenshot is the average since the beginning of the day GMT (2019-01-15 00:00 GMT). So it should not be exactly the same. That being said, we just fixed one bug with the calculation but I think it is still incorrect somehow. For me mining at 0.64 MH/s the calculator predicts ~30 blocks per day for a network hashrate of (~45 MH/s). However, I have only mined 60 blocks since about 1/12/2019 12:00 GMT. The current time is 1/15/2019 16:00 GMT, so that is only 60 blocks in 76 hours (~19 blocks/day). I expected it to be somewhat less than predicted since there are actually only ~2747 blocks/day mined instead of the targeted 2880, but that is not enough to account for the difference. -
Xaya-Gaming.net Main Site Launch *BACK ONLINE* | *Liquid.com Trade Data* + *Blockreward Info* added
sorji replied to casp0or's topic in General
Hi @casp0or I find the hashrate in your web is not match with the xaya console, so we have wrong earning by using th mining calculator -
NMC is listing in below exchange I‘m the holder of huntercoin before snapshot， finally we got the 0.23338CHI/HUC compare to the 3 CHI/HUC, that's 13X gap/lost who buy the huntercoin for exchange the CHI if HUC = 0.003 mBTC then CHI = 0.039 mBTC(13x) also cost of sold coin (ICO participants) CHI = 0.01095 mBTC(31308092/(304.6btc+798ETH)) so no matter how we calculate, 0.005mBTC/CHI is a good deal
-
First, converting to mBTC (I find it easier to read): NMC = 0.199 mBTC HUC = 0.003 mBTC CHI = 0.005 mBTC According to our stats (http://xaya-gaming.net/), despite it being a new coin there's 47 million chi already in existence. About 10 million of those are currently held by the xaya team. So lets say 37 million available for trading. In contrast, there are about 23 million HUC, and 15 million NMC. Meanwhile HUC and CHI prices are about the same and NMC is ~50x higher. But there are only 1.3 million in the liquid cold wallet and 1.1 million for sale on the order book (~2%). Also, on polo I see about 650k NMC (~4%) and 7m HUC (~30%) on the books. I see two ways of looking at it: Looking at overall supply, if there were equal demand, we'd expect HUC to be ~ 2/3 the price of NMC and CHI to be 2/3 of HUC (~40 % of NMC). Using NMC as the basis: NMC = 0.199 mBTC HUC = 0.134 mBTC CHI = 0.087 mBTC Using the number of coins on order books as a measure of sell pressure (not sure if NMC is on other exchanges though), we would expect CHI to be ~ 60% the price of NMC and HUC to be ~10-15% of those two. Once again using NMC as the basis: NMC = 0.199 mBTC HUC = 0.020 mBTC CHI = 0.119 mBTC So if we ignore the demand I can kind of see what you are saying (CHI should be with in a factor of 2 of NMC), but as we can see from the NMC/HUC price disparity that is ignoring a huge factor... Also, not sure why the richlist on the site isn't updating, so here is the most recent showing what I am talking about (top 15): address current first_in last_in first_out last_out note 1 0000000000000000000000000000000000 175,839,877 285,633 318,785 NA NA Burned coins 2 DHy2615XKevE23LVRVZVxGeqxadRGyiFW4 7,680,271 0 338,223 1 338,223 Xaya team: Premine (10% final supply) 3 chi1qah5cwrswaufmmutc7eduh453a6cpac5vupwrkd 2,317,538 285,732 502,250 285,931 502,250 Xaya team: Uncollected presale coins 4 CPR4dDAPSHYWBYr6nZMhoy4prkRA9WZxgf 1,500,001 253,261 277,680 NA NA <NA> 5 CXaB6a5qJ1W18kAn9PD1YbWJ6MXkEzpGLN 1,319,950 320,923 320,923 NA NA <NA> 6 CJwvs9JuqcskANChNinZZWzkcYhp4M2EB5 1,316,850 297,458 297,458 NA NA <NA> 7 CH7RjcL2FmF2Tu222abyv1tHx8bSnXH7y1 1,296,412 287,820 507,056 287,869 507,056 Liquid Exchange: Cold wallet 8 CRmn7rBsMg4VDEBu5nbRqwZxmaKj8jfNae 1,100,000 289,047 289,047 NA NA <NA> 9 CM9U2WGYxFuS26uuqGCfJH8HqqEyNnpPvj 900,245 289,047 289,047 NA NA <NA> 10 CaS7G5pDmbk2gKeG7GMT7NyoAYQ1xpQ6Xh 799,950 299,111 299,111 NA NA <NA> 11 CXY12KC6xw2SokjUuWFCvJZCXU64Aeoeqc 760,001 45,171 250,608 NA NA <NA> 12 CRy3N9y1zXTWqPXXdavYUkL3AJavzbEmpF 618,015 277,669 301,105 NA NA <NA> 13 CNbWcG1JQUvtNdduGG7NArnTTKVtkimD6s 574,048 265,415 271,559 271,555 271,593 <NA> 14 CcmUfvfFhT2RszPoczW4E9reD9EiaFo3zG 568,799 285,604 285,604 NA NA Received HUC airdrop 15 chi1qzpeqgsgcw7q9hrysa89d5u7z56wgs3sg5aj6an 555,520 315,731 422,812 315,854 422,812 Xaya team: Bounty address
-
I made some research yesterday and I hope I can solve the problem today 👍 Regards
-
Well know that u will be the 1st place to get 20K CHI pool setup reward. Come On. My friend and I still unable to sort the issue, i can use your pool for mining.
-
Base on current sell wave on liquid, most like miner who solo most of the coin is cashing out those days. it will change soon when pool ready, when the AMD rig can join the mining, they will not get the most share anymore. no reason that namecoin=0.00019911/huntercoin=0.00000333, and CHI only 0.00000463(2019-01-14 03:42 UTC) Hope you can collect the CHI for your bid.
-
Mods: This one should probably be moved to trading as well.
-
I'll be willing to buy up to 10k CHI at 0.000005 BTC (.05 BTC total). Post here if interested and we can figure out the safest way to do the transaction. Also, to mods: is it possible to create a trading sub-board?
-
Yes, the rewards haven't been sent yet, just wait 😉
-
I'd think xaya is more innovative/interesting than the typical alt-coin that this policy is meant to defend against, but maybe everyone says that about "their" coin... If you guys do contact Bisq about listing you may as well try to get HUC on there too though.
-
Lwin Phyn joined the community
-
guys, the blocks are completed, and the 4th round tokens never came, do you have to wait?
-
Thank you very much guys! Thanks for the good answers! Only the progress of the blocks is now moving for a long time, probably it should be)
-
ahh ok 👍 I check my xaya.conf soon thanks I got overall 15Mh/s currently running for xaya on my local net. Using currently 6Mh/s from this to search for a block on the pool. Should not last longer than 10-20 minutes to find a block
-
if port 8394 is closed the client gets a max of 8 connections (outgoing connections limited to 8). If open port - should get loads of incoming connections (should be open for pool as well so there is more chance for people to receive your blocks before someone elses, and so you can receive theirs so you don't waste a second or so carrying on mining looking for next block).
-
lol, maybe I have found the issue with the diffTarget 🤦♂️ used the calculated diff number instead of the nbits for the specialPoW diff field... maybe this will work Now I have to wait for the next block to be found
