@gatra
I am now receiving the following error message with your latest Windows client while on testnet:
block with too much proof-of-work
However, the original Windows client works fine, any ideas?
maybe because I didn't put any valid checkpoint for testnet... please try running riecoind with "-checkpoints=0" besides "-testnet" |
|
|
|
Zipped windows wallet seems to be corrupted I couldn't unpack it.
Thanks and sorry! I uploaded it again, something must went wrong during the upload. Just in case, SHA1 hashes before uploading to sourceforge: 5ac81d76d6f5932a29cacda5755acdde1523c394 *riecoin-0.8.7-sources.zip 3ab4ab66df4540fb634d0f437d5f7e53f6e55c6b *riecoin-linux-32.tar.gz 917b32f8346a688f15e26d8c8276f61fcca1ef9b *riecoin-linux-64.tar.gz fcf237ff0ee486ff7414c142bf9ca7885248f3f8 *riecoin-win32.zip Thanks and regards, gatra |
|
|
|
Thanks for the update!  Boost of confidence right there. But any future plans? Maybe incorporate coin mixer or something? Just curious. Sorry if it sounds rude. Of course I'd like to add as many features as possible, but it's been less than 2 weeks and there is no p2pool yet. Let's give it time to mature. Maybe you (or anyone) could start a poll or a discussion on wanted features for the future, so I could use it as a guide. Current plans are p2pool first and block explorer and gpuminer next. |
|
|
|
Hey dev, since you're online, care to post what the plan is from here? Any other plans to make this coin a lot more unique?
New client version released, with more uniqueness: "the first coin with an official release addressing the transaction malleability problem". ypool is getting all the blocks (btw this proves there is no super secret super solo super miner), which doesn't look good for decentralization. The priority is getting other pools online. After that, we'll look good for major exchanges and we'll be ready for prime time! I'd like to thank all the poeple for the support and interest put in Riecoin! gatra |
|
|
|
More regarding the transaction malleability issue: The new option is a workaround for the problem. By default spendzeroconfchange is 1, meaning the behavior would be the same as before. If you want to activate the new feature run with "-spendzeroconfchange=0", this will prevent spending unconfirmed change which is what creates transactions that could never confirm if a conflicting tx is broadcast. This feature is off by default because it can lead to unfriendly behavior: the reported balance may not be all spendable until your change is confirmed. So, please use it only if you know what you are doing. This should only affect you if you send more than once per block. Please read https://github.com/bitcoin/bitcoin/pull/3651. |
|
|
|
Hi people! This is to announce a new version of the client. This is not a hard fork, but it should be considered a mandatory update because it addresses security issues. Downloads link: https://sourceforge.net/projects/riecoin/files/riecoin%200.8.7/?And of course sources at https://github.com/riecoin/riecoinSite: riecoin.orgList of changes: - fixed logo and icons for Windows binaries
- added option -spendzeroconfchange to workaround tx malleability problem as in https://github.com/bitcoin/bitcoin/pull/3651
- added seed nodes
- added checkpoints
- Chinese translations fixed
- difficulty field in getinfo, getmininginfo, getdifficulty now return the same as getwork: the size of the primes measured in bits. Note that this is not linear: 1500 is not 3x harder than 1000. It's like 700 times harder
- fixed DoS (crash) vulnerability in PoW calculation
Are we the first *coin with an official release addressing the transaction malleability problem? of course I "stole" it from Bitcoin, but still... Since this is a security update, plase make it sticky for some hours. Is there a place to request that? |
|
|
|
Because of the variance in success and some quirks of the search, here's a patch to let people have a little more visibility into how the miner is doing: http://www.cs.cmu.edu/~dga/rie_log.patchTo use, download the miner source and cd (your-source-directory) patch < rie_log.patch You should see log output whenever the miner finds a chain of length 2 or longer. Look for roughly a 10x difference in length 2, length 3, ..., blocks in your output log over time. If you're *not* seeing any length N chains -- because, e.g., you've broken something during optimizing -- then you know something is wrong. I've found that the rate of generating length 2 or 3 chains is a good backup benchmark to use. Gatra, please feel free to have full ownership of the patch - I release any copyright claims to it - if you want to include it or something like it in the default miner. -Dave nice, will take look at it. Have in mind that the 10x may vary with difficulty. |
|
|
|
thank you all offering servers, I'll get back to you when I have some code to share
Could you generate / manage addresses for donations? Not for silly crap like spamming Cryptsy, but for code, pools, etc. I'd be willing to throw some RIC and/or BTC into the fray. Donations are always welcome. The addresses are the ones listed in riecoin.org: RIC: RByJXMhtRa2Jc2ix6sWoVRZq3kyK3zb8nY BTC: 1Ud6xgvXwKGksbguVgke8UTbJ9sYr9AuH I do code, and I'll maintain the client, miners and give support to pools and p2pool. I'm against paying to get into exchanges. The cpuminer works fine, no errors on scanhash_riecoin, but I realize some optimizations could be done. I'll look into that tomorrow but don't expect huge improvement. Thank you. |
|
|
|
|
thank you all offering servers, I'll get back to you when I have some code to share
|
|
|
|
|
Hi people!
I'm offering support for people who want to set up pools (since I don't have the servers or time to operate a pool myself), but please have some specific questions, not like "how do I set up a pool?"
jh00 from ypool told me he is working on adding support for riecoin. He's making good progress, and looking at the work he did with primecoin he probably won't need my help.
I understand that the lack of pools undermined the fairness of the launch, but that will be corrected.
thank you all
gatra
|
|
|
|
|
How to calculate network scanrate or processing power ("hashrate" does not apply: we are not hashing, we are scanning ranges of numbers in search for prime sextuplets):
scanrate = pow( diff * ln(2), 6 ) * 0.05780811 / 150
Where diff is the difficulty as shown in "getwork", currently 776
so scanrate is 9.3 TeraNumbers per second
Divide that by your total knumbers (careful with units: T vs K) per second and you get how many systems like yours would comprise the total network.
I guess 40000 i5 with 4 cores @ 2.6MHz each, or 160000 cores?
Please check the math and correct me if I'm wrong.
This is the reverse of what is calculated in riecoin_time_to_block() in scanriecoin.c in the cpuminer.
Have in mind that scanrate SHOULD ALWAYS BE COMPARED AT THE SAME DIFFICULTY. Since the scanrate decreases as difficulty increases. So it's ok for relative measurements of common difficulty, but has to be normalized if you want to compare at different prime sizes (difficulties).
If in the future we go from 9 to, say, 5 it doesn't mean the network grew or shrinked, it means nothing if values are not normalized for difficulty. Theoretical normalization for difficulty is possible but hard and would introduce errors. The easy way to do it is to actually measure in practice, relative to your PC. Like I did: currently it's about 160K cores and that's the value that's comparable in time.
|
|
|
|
I will say that since the standard for coin launches is so incredibly low, this was, by comparison to the vast majority of shitty altcoins, a good launch. I still don't understand why devs feel the need to set an arbitrary date and time to launch without having any clue whether or not their coding will be ready by then. Why not finish coding BEFORE launching?
Coding was done days ago. But the genesis block must include some news or something public from a date close to the launch to PROVE that you didn't keep the client for yourself and mined it in private. So after you set that, you have to recompile. For all platforms. 32 and 64 bits. If something goes wrong, you are in trouble. It is done this way to avoid premining in private and then forcing a reorganization by publishing your secret blockchain.... I was setback because I used gitian to compile, which is really cool, but if something goes wrong each compiling attempt is very slow and it can be a PITA. I'd say the launch itself was not as I wished, but still acceptable, except for the distribution problem. If it's hard to find a block it's not my (or anybody's) fault, it's because people throw a lot of processing power at this, but they are investing a lot too. The problem is I didn't foresee pools were so necessary.... |
|
|
|
|
Hi!
I'd like to thank all the people how participated on the launch yesterday. There were some problems, but overall I think it was an acceptable launch.
Some lessons I learned on my first cryptocoin lunch:
- The first blocks without reward seemed silly (who would mine for nothing?) but it turned out to be a good idea. Good for testing everything is working.
- Binaries must be ready from the start, or rogue wallets with virus might spread. I'll forget about this thing that the coinbase should have some recent news, the best is to have everything ready at the time of announcing the launch. To avoid premine, let everyone with blocks with 0 reward be the witnesses that the chain wasn't started before.
- Hard starting difficulty is good. It's fair. But.... (see next point)
- ...pools really are really important! I thought that pools where bad, agents of centralization, and that distribution "on the long run" would be the same if pools didn't exist, but now I understand that they are needed for good distribution of the coins, because "on the long run" difficulty changes and smaller miners cannot compete.
-Always keep people informed of what's going on!
- Be wary of giving estimates! As a developer I used to be good at estimating effort. The thing is that even if effort estimates are correct, I cannot estimate when will I be able to put that effort in practice. I have a job and 2 kids IRL, I love them and they take a lot of my time... (and I'd like to thank my wife for her help while I'm working on this) the point is my failure was at predicting how many hours I can put on this.
- I can't do this alone. I need a team.
- I won't make money with this. Need to think more carefully about monetizing.
- What else? please comment
Things to fix in the next release:
- On the rush to launch, windows wallet came out with bitcoin logos
- On getinfo and getmininginfo, the difficulty is rounded to the integer. The difficulty in getwork (field diff) is the size of the primes, and it works ok. But the difficulty in the getmininginfo and getinfo commands should be the ona on getwork divided by 304 which is the minimum difficulty. So it started at 1, but the thing is that it's an integer division so it's not much useful.
- Add checkpoints and seed nodes
- What else? please comment
Where to go now?
- We need a pool urgently. I'm working on a p2pool and will give support to those how want to implement pooled mining.
- Please promote! we need services, exchanges, everything. Go to your altcoin payment service provider and ask for riecoin. Go to your exchange and ask for riecoin. Go to your mathematician and ask him to take a look at it, etc
- should we go like "so numbers", "such prime", "much sextuplets", "the Chinese are in", "to da moon!"... does that work?
- Please contribute: we need a block explorer
Please help me make this work!
Thank you!
gatra
|
|
|
|
|
Hi!
To the winner of the contest: Mjbmonetarymetals, please send me your RIC address so I can award you the prize!
Sorry the logo didn't make it into the Windows wallet, in the rush for launching the Linux wallet is ok but the Windows version was published with the bitcoin logo. I'll fix that for the next release.
Thanks and regards,
gatra
|
|
|
|
|
I'll leave you some nodes and go to sleep...
addnode=107.170.26.188
addnode=107.170.32.187:28333
addnode=107.170.37.13
addnode=107.170.40.168:28333
addnode=108.161.145.12:28333
addnode=162.243.118.47:28333
addnode=162.243.208.55
addnode=162.248.98.162
addnode=173.193.48.174
addnode=182.32.194.1
addnode=192.241.129.169
addnode=194.97.156.59:28333
addnode=195.47.113.76:28333
addnode=198.144.180.117
addnode=198.144.180.118
addnode=198.98.52.244:28333
addnode=213.239.207.114:28333
addnode=5.83.137.130:28333
addnode=5.83.137.131:28333
addnode=54.197.67.63
addnode=54.198.193.96:28333
addnode=54.204.214.12
addnode=54.234.17.173
addnode=54.237.23.244:28333
addnode=62.210.141.204:28333
addnode=64.79.107.5
addnode=67.225.172.77
addnode=76.102.71.50
addnode=77.172.93.38:28333
addnode=79.135.200.61
addnode=81.27.206.10:28333
addnode=95.138.166.108
addnode=95.138.166.126:28333
addnode=98.121.202.169
|
|
|
|
|
Show Posts
