Gatra, what are you waiting for with the wallet fixes ?!
Posted on 23. Apr :
Worst client ever! Takes 2 minutes to start on an i7. 5 minutes when using -rescan arg. Fresh install/syncing the blockchain takes longer than bitcoin...
Dev, fix the client. this is ridiculous..
EDIT : Forgot to mention, keep the wallet running for a couple of days, interface says connected. Try to send coins - unable/offline.
EDIT2 : Try to rebroadcast an offline transaction using -rescan, nothing happanes after 30 min! Now i have to export/import priv keys !! Shittiest out of all ALT wallets!
I did noticed it was slower than bitcoin wallet. Could it be due to the data size needed to store the long prime digits? Progressively, it will require alot more disk space? Hey, I'm not waiting, it's just that it's a lot of work. The extra data is minimal, the overhead is in the verification - which will be optmized a lot in next version. Also, since v0.9.1 block headers are downloaded before the rest of the blocks, this allows for block downloading in parallel, which will further speed up the sync process. EDIT: not only the extra data is minimal, it will remain constant regardless of prime size increasing because only a 256bit offset for the first prime in the tuple is stored. |
|
|
|
I need help on the Android Wallet App for Riecoin. Trying to Find parameters for some of the following:
proofOfWorkLimit = Utils.decodeCompactBits(0x1d00ffffL); //help
dumpedPrivateKeyHeader = 128;
addressHeader = 60;
p2shHeader = 5;
acceptableAddressCodes = new int[] { addressHeader, p2shHeader };
port = 28332;
packetMagic = 0xfcbcb2dbL;
genesisBlock.setDifficultyTarget(0x1d00ffffL); //help
genesisBlock.setTime(1231006505L);
genesisBlock.setNonce(2083236893);
id = ID_MAINNET;
subsidyDecreaseBlockCount = 840000;
spendableCoinbaseDepth = 100;
String genesisHash = genesisBlock.getHashAsString();
checkState(genesisHash.equals("e1ea18d0676ef9899fbc78ef428d1d26a2416d0f0441d46668d33bcb41275740"), //help --NEED confirmation
genesisHash);
// This contains (at a minimum) the blocks which are not BIP30 compliant. BIP30 changed how duplicate
// transactions are handled. Duplicated transactions could occur in the case where a coinbase had the same
// extraNonce and the same outputs but appeared at different heights, and greatly complicated re-org handling.
// Having these here simplifies block connection logic considerably.
checkpoints.put(91722, new Sha256Hash("00000000000271a2dc26e7667f8419f2e15416dc6955e5a6c6cdf3f2574dd08e")); //help- How do I know which one in RIC are non-BIP30 compliant.
checkpoints.put(91812, new Sha256Hash("00000000000af0aed4792b1acee3d966af36cf5def14935db8de83d6f9306f2f"));
checkpoints.put(91842, new Sha256Hash("00000000000a4d0a398161ffc163c503763b1f4360639393e0e4c8e300e0caec"));
checkpoints.put(91880, new Sha256Hash("00000000000743f190a18c5577a3c2d2a1f610ae9601ac046a38084ccb7cd721"));
checkpoints.put(200000, new Sha256Hash("000000000000034a7dedef4a161fa058a2d67a173a90155f3a2fe6fc132e0ebf"));
//help BADLY dnsSeeds = new String[] {
"seed.bitcoin.sipa.be", // Pieter Wuille
"dnsseed.bluematt.me", // Matt Corallo
"dnsseed.bitcoin.dashjr.org", // Luke Dashjr
"seed.bitcoinstats.com", // Chris Decker
};
I marked the parameters I need help in with //help
Fortunately all blocks are and will be BIP30 compatible because the "enforce BIP30" option is on by default since the first RIC release. The only checkpoint that you need is the one at 4000 (see checkpoints.cpp). I'll add more for the next release but it's not mandatory that you include them. Regarding the genesis block hash, e1ea18d0676ef9899fbc78ef428d1d26a2416d0f0441d46668d33bcb41275740 is correct For the genesis block, difficulty should be 304, which is 0x02013000 when packed (there is no concept of "target" on RIC, only the difficulty). The nonce for the genesis block is 0. The genesis is a special case: it's the only block that doesn't have primes. This saved me the trouble of mining it. You can leave dnsSeeds empty and then add some nodes manually. If you uploaded the code to github or something, I could help you with some of these details Different question Gatra, I noticed that in main.cpp, nBits= MinPrimeSize.GetCompact(); How would I put this is android code? MinPrimeSize.GetCompact() is just 0x02013000 So I think it would be genesisBlock.setDifficultyTarget(0x02013000L); |
|
|
|
So..an exchange owner can use our bitcoin to claim these bootstrapped coins?
haha... very true! I think it would be best to bootstrap not using holders of BTC, but using only mined BTC - ie the private keys of the coinbase transaction regardless of whether those coins were later spent or not. Reward actual miners of BTC instead of current holders! The downside is that if the miners already spent the coins then it's likely that lots of those private keys are lost. Also, it works with p2pool, but in a traditional pool the owner could use your mined coins to claim these bootstrapped coins... OTOH you already trusted the pool OP with your hashrate once, so it would be acceptable to assume you'd to trust them again... I guess this reasoning would apply to the proposed case... if you trusted the exchange with your BTC it would seem acceptable to assume you'd trust them your bootstrapped coins... |
|
|
|
New paper wallet design on riecoinfoundation.org/PaperWallet. Check it out! Credits go to our wonderful foundation member, Antoine who made the design!  Thank you Antoine! I love it! I'll print a couple... great job! |
|
|
|
Hey Gatra, can you remove Cryptokk from exchange list? They supposedly got "hacked"
done! thanks for letting me know |
|
|
|
northranger is spot on with RIC. It is not a coin that a traditional pump and dump or scam feature coin. It provides, real, sustainable additions to the science community. To that end, a fast explosive growth pattern would not be conducive to stable, long term growth. Future development would include stratum support for sure and the addition of more pools to increase mining adoption rates.
At least I think that's what we are going for?
yep, useful features (like coin control) will be included, but I think we don't need PoS or decentralized exchanges (at least as they are currently implemented in other coins) or other features which I consider of "dubious fairness" (requiring IPOs or skewing rewards in an obscene way towards early adopters). we do have a huge list of developments to do compiled in riecontalk, right? |
|
|
|
The params I see on the repository are identical to the originals from bitcoin. Are you sure you pushed all your commits? which branch are you developing on? |
|
|
|
Thursdays come by soo quickly.
I couldn't agree more... I'll mention some of the features of the new client so everyone can understand why it's taking so long: - Coin Control! if you want to, you can choose the inputs for your tx when you send RIC - Payment requests - this is a whole new world: we'll have "riecoin:" URIs - new makefiles (autotools): build with "./autogen.sh; ./configure; make" - New receive coins workflow, with invoices And all of these that can we applied to RIC will be applied: https://bitcoin.org/bin/0.9.0/README.txtOf course the new openssl will be used, and we'll have Riecoin specific optimizations. |
|
|
|
I need help on the Android Wallet App for Riecoin. Trying to Find parameters for some of the following:
proofOfWorkLimit = Utils.decodeCompactBits(0x1d00ffffL); //help
dumpedPrivateKeyHeader = 128;
addressHeader = 60;
p2shHeader = 5;
acceptableAddressCodes = new int[] { addressHeader, p2shHeader };
port = 28332;
packetMagic = 0xfcbcb2dbL;
genesisBlock.setDifficultyTarget(0x1d00ffffL); //help
genesisBlock.setTime(1231006505L);
genesisBlock.setNonce(2083236893);
id = ID_MAINNET;
subsidyDecreaseBlockCount = 840000;
spendableCoinbaseDepth = 100;
String genesisHash = genesisBlock.getHashAsString();
checkState(genesisHash.equals("e1ea18d0676ef9899fbc78ef428d1d26a2416d0f0441d46668d33bcb41275740"), //help --NEED confirmation
genesisHash);
// This contains (at a minimum) the blocks which are not BIP30 compliant. BIP30 changed how duplicate
// transactions are handled. Duplicated transactions could occur in the case where a coinbase had the same
// extraNonce and the same outputs but appeared at different heights, and greatly complicated re-org handling.
// Having these here simplifies block connection logic considerably.
checkpoints.put(91722, new Sha256Hash("00000000000271a2dc26e7667f8419f2e15416dc6955e5a6c6cdf3f2574dd08e")); //help- How do I know which one in RIC are non-BIP30 compliant.
checkpoints.put(91812, new Sha256Hash("00000000000af0aed4792b1acee3d966af36cf5def14935db8de83d6f9306f2f"));
checkpoints.put(91842, new Sha256Hash("00000000000a4d0a398161ffc163c503763b1f4360639393e0e4c8e300e0caec"));
checkpoints.put(91880, new Sha256Hash("00000000000743f190a18c5577a3c2d2a1f610ae9601ac046a38084ccb7cd721"));
checkpoints.put(200000, new Sha256Hash("000000000000034a7dedef4a161fa058a2d67a173a90155f3a2fe6fc132e0ebf"));
//help BADLY dnsSeeds = new String[] {
"seed.bitcoin.sipa.be", // Pieter Wuille
"dnsseed.bluematt.me", // Matt Corallo
"dnsseed.bitcoin.dashjr.org", // Luke Dashjr
"seed.bitcoinstats.com", // Chris Decker
};
I marked the parameters I need help in with //help
Fortunately all blocks are and will be BIP30 compatible because the "enforce BIP30" option is on by default since the first RIC release. The only checkpoint that you need is the one at 4000 (see checkpoints.cpp). I'll add more for the next release but it's not mandatory that you include them. Regarding the genesis block hash, e1ea18d0676ef9899fbc78ef428d1d26a2416d0f0441d46668d33bcb41275740 is correct For the genesis block, difficulty should be 304, which is 0x02013000 when packed (there is no concept of "target" on RIC, only the difficulty). The nonce for the genesis block is 0. The genesis is a special case: it's the only block that doesn't have primes. This saved me the trouble of mining it. You can leave dnsSeeds empty and then add some nodes manually. If you uploaded the code to github or something, I could help you with some of these details |
|
|
|
Btw Dev, can you add the google play links I posted on here on OP as well as the paper wallet/multisig generator?
done great work! I'm addicted to the widget... |
|
|
|
|
Riecoin just got listed! yay!
nice site, I like the twitter and reddit boxes
thanks!
|
|
|
|
I'd like to know how fast the new client will be compared to say...Litecoin? Slower or faster?
I'm answering before we leave the first page  It's a fair comparison because LTC has blocks each 2.5 mins as we do, but it's not fair because LTC's PoW is not "useful"..... Anyway the answer depends on the current RIC difficulty. The first sync will definitely be much faster in RIC and in LTC, because LTC has much more blocks, and it will be like that for some time. If RIC difficulty goes up by a big amount this may change. and we would need to look at some more aggressive optimization. |
|
|
|
but everybody can download vmware player (or other virtualization solution) for free and try any linux distribution (e.g. fresh ubuntu 14.04 long term support and user friendly) for free - and here we go  To my surprise, the penalty of using the miner with ubuntu inside vmware on a windows 7 host versus the windows miner was really small edit: I'm talking about my rminerd 3.1.1 - YMMV |
|
|
|
I think what can help a lot right now are community members posting on this thread daily to keep it on the first page constantly.
I completely agree, I'd just like to add that it would be much better if we could have real ideas, comments, questions, problems or solutions instead of nonsense messages... come on, there should be a lot of people with real RIC issues to discuss, don't be shy! |
|
|
|
Hey Gatra,
will the next client fix OpenSSL problem?
Yes! |
|
|
|
Hi Riecoiners!
I'm woking on a new client version that will include changes from Bitcoin 0.8.6 to 0.9.1 besides some Riecoin specific speed improvements. It's a lot of changes, and Bitcoin has changed so much that cherry-picking or rebasing commits results in lots on conflicts that have to be manually merged, that's why it's taking longer than expected, but the good news is that we'll have a much better client soon.
There will be a Windows installer, and also 32 and 64 bits versions for Windows. This means block verification will be much faster for Windows users with 64 bits CPUs and OSs.
Regarding the miners, keeping miners updated with all the latest optimizations is a lot of work so I'll focus on an xpt to stratum proxy.
gatra
Thanks Gatra! Would the 0.9.1 include the improvements from dga's xptminer? Also, would there be an independent solo miner that incorporates dga's improvements? or does it make sense to have an xpt to stratum & GetBlockTemplate proxy? I'd rather keep the miner embedded in the client as simple as possible, so it works as a reference of what does the miner calculate. An xpt to GetBlockTemplate proxy is a nice idea, I'll look into it |
|
|
|
|
Hi Riecoiners!
I'm woking on a new client version that will include changes from Bitcoin 0.8.6 to 0.9.1 besides some Riecoin specific speed improvements. It's a lot of changes, and Bitcoin has changed so much that cherry-picking or rebasing commits results in lots on conflicts that have to be manually merged, that's why it's taking longer than expected, but the good news is that we'll have a much better client soon.
There will be a Windows installer, and also 32 and 64 bits versions for Windows. This means block verification will be much faster for Windows users with 64 bits CPUs and OSs.
Regarding the miners, keeping miners updated with all the latest optimizations is a lot of work so I'll focus on an xpt to stratum proxy.
gatra
|
|
|
|
Bitcoin is 0x00 for publickey and 0x80 for the private key.
Anyone know what pub and priv key for riecoin?
What is the mainnet for Riecoin?
I need this for the android app I am working on for Riecoin.
We use 60 (0x3C) as the prefix for public key base 58 representations. Still 0x80 for private keys. What do you mean by "What is the mainnet"? this? The protocol version is hardcoded to 10070001 and the protocol's "magic" number is 0xdbb2bcfc, and 0x0511090d for testnet. Since I am a lazy person, can you tell me what the mainnet is for script hash address? I know Bitcoin is 0x05. I assume Riecoin is also 0x05 but I want to confirm. Yep, it's 0x05 btw that's why the Foundation's multisig address starts with 3. |
|
|
|
|
Show Posts
