 Show Posts
|
|
Pages: « 1 [2] 3 4 5 6 »
|
Upcoming Major Riecoin 0.20 UpgradeA new major Riecoin upgrade is planned, and includes a hard fork. I worked on it during the last few weeks. The first step of this upgrade was to update the base code to Bitcoin's 0.20, which is done. You can find the experimental code at the Github repository. I also built experimental binaries. Despite their prerelease status, they should work fine and be fully compatible with current 0.16 nodes, though please backup your wallets if you plan to use 0.20, just in case. Feedback is welcome! Pool operators and other advanced Riecoin users should start looking into the changes and update their software accordingly, as well as closely follow the Riecoin Core development. Here is a list of notable changes from 0.16.3.1. - There were inconsistencies regarding the nTime and nBits positions in the Block Header. For example the SubmitBlock and GetBlockHeader commands were inconsistent regarding this. This is now fixed, with nTime always coming before nBits like for Bitcoin. Internally, when hashing for mining or to get a block hash, nBits must still come before nTime (I really don't know what Gatra did, this swap was just unnecessary). Riecoin related software should be updated accordingly. This includes rieMiner, which current stable version is no longer compatible with 0.20, but the latest source code is;
- Testnet was reset. I only know about 2 active Testnet nodes, and both forked for some reason, so it was clear that a fresh start was needed. Additionally, the constellations for Testnet are no longer sextuplets, but quadruplets, and the minimum Difficulty was raised to 600 rather than 304. Testnet nodes are needed, as well as continuous spare mining power to mine test blocks and make Testnet a decent simulation of Mainnet. Please use the Testnet bootstrap found here;
- The "getnetworkhashps" command was replaced by "getnetworkminingpower" (and fixed: previously it only relied on the current Difficulty, now it works properly with lookup blocks). A new metric is used, and is standardized such that 1 correspond to mining a minimum difficulty block (Difficulty 304 in Mainnet or 600 in Testnet) every 150 s. For now it is proportional to the Difficulty^(constellationLength + 2.3), in accordance to observations with rieMiner; the formula may be improved later at any time. The Block Proofs/Chainwork are also now using a similar calculation;
- The GetBlockTemplate's "primes" field is replaced by "constellations", which gives a list of accepted constellations for mining rather than just a constellation size. The "segwit" rule is now mandatory;
- The "getprimes" RPC call is replaced by "getresult" and gives directly the base prime number, instead of all the prime numbers. It will be completed later to include information about the PoW;
- Generated addresses are now Bech32 by default;
- The RegTest is now properly implemented (the PoW here is simply prime numbers). Most of the test units were ported to Riecoin;
- And of course, all the Bitcoin features and bug fixes since 0.17 are now included in Riecoin. Read the Bitcoin Core change logs for more information.
The base code upgrade is pretty much done, though some help is still needed in order to complete the build system and the test units. No seed node nor DNS seed node IP were hardcoded yet, so one needs to add nodes in the riecoin.conf (there is a template in the binaries page). Please support the network by providing reliable Riecoin nodes and DNS seeders for the long term and share them for hardcoding! This will make initial sync possible without having to add some nodes in the configuration file. The next step will be the hard fork, in order to improve Riecoin in multiple ways. Early discussions took place here, as well as in Discord and a few posts here somewhat far in the past. Here are planned changes. - The constellation pattern will be changed from sextuplets to septuplets (quintuplets in Testnet). Both possible patterns will be accepted, so the blockchain will provide more diverse results. One of them will have a chance to be a 8-tuple or longer, which would help a lot to beat records and improve the Riecoin's scientific usefulness. In contrast, the sextuplets cannot be part of longer tuples, which is really a shame. Moreover, longer constellations are also better because they make verification even easier in comparison to finding them, which make them more practical as PoW;
- The SuperBlock system will be removed. While records have indeed been broken this way, it also has significant drawbacks, like freezing the network during an hour every week and a complicated implementation that also confuses a lot of people;
- The Difficulty Adjustment Algorithm will be improved. No particular algorithm has been chosen yet. The chosen one should not be too complicated to implement, while improving resistance to attacks like Selfish Mining or Timestamp Manipulations, proposing smooth Difficulty updates (often enough and without sudden variations) and well respecting the 2.5 minute average for the long term. The discussion is open and DAA Suggestions are welcome!
- The nOffset encoding will be updated in order to allow offsets > 2^256, which allows more efficient mining. Some PoW information like the constellation type may also use this field. See a former rieMiner's developer suggestion about this.
Once the development is advanced enough, a date will be chosen for the hard fork. Testnet will be hardforked first to ensure the well functioning of the implementation (that is also why a proper Testnet network is needed). Stay tuned! By the way, I am thinking about creating a new BitcoinTalk topic with updated first post (it is clear that Gatra will never come back to update the post, and having outdated information in such an important post does not give a good image of Riecoin and is a source of confusion), and will proceed soon unless some community members are opposed to this.
|
|
|
|
New Mining Calculator available to estimate very quickly and roughly the earnings. Turns out Riecoin Mining can be surprisingly profitable... |
|
|
|
Hi guys. can we have a telegram channel in which to chat with others that are interested in Gapcoin? thanks
Would prefer Discord if possible J +1 Cheers Graham I just opened a Gapcoin Discord ( invite). If someone actively involved in Gapcoin would like to get Mod/Admin roles, just send me messages in both Discord and BitcoinTalk. Else, I would be glad to manage this Discord as I do for Riecoin. For now I use similar layout and rules as the Riecoin Discord. You need to post something in #Welcome in order to be able to post to all channels. |
|
|
|
My focus is now firmly on increasing adoption, following some new exchange listings, hopefully.
https://c-patex.com/voting-en.phpOn April 15, 2020 the voting will be closed and will be THE LAST OF THE YEAR
Coins that have earned 5 or more votes, or have deposits of 0.1 LTC or more, will be added in the next few weeks Maybe a good chance to get Gapcoin listed in a second exchange, either for free if you can convince 4 people using the exchange to vote or cheaply if you can send 0.1 Ltc to the vote address. |
|
|
|
Again, in GitHub: You can then spend it after 100 confirmations The wallet also says how many confirmations are left... |
|
|
|
|
There is already a full and detailed example in the GitHub page. In particular, it is clearly mentioned that the case mattered. And both "Mode = Solo" and "Mode=Solo" would work without issue...
Yes, the miner is not supposed to be installed in /usr. Just put it wherever you want in your /home directory...
With 6 GiB of RAM, try PrimeTableLimit = 1610612736, and if it is using too much memory, use 1073741824.
Try SieveWorkers = 1 and monitor CPU usage, ensuring that it is most of the times at 100%. If there is a noticeable CPU Underuse, increment the number until you find the sweet spot.
Try values between 23 and 26 for the SieveBits and choose the sweet spot.
|
|
|
|
|
If your username or password contain spaces, that might cause such issue.
Otherwise I don't really see what could cause this, please tell us in this case more (your OS, riecoin.conf and rieMiner.conf contents,...)
|
|
|
|
Hello everyone!
If i do regular mining can i run for the record or must be only in the benchmark mode, and if i find the block in benchmark mode is it seen in the wallet?
join discord and ask Pttn there for a faster response It must be the Benchmark Mode. We would need much more miners to hope to break the 6-tuples record by mining RIC. No block is mined in Benchmark Mode, it is independent from the Riecoin blockchain. And yes as Pon13 said, if you wish to beat a world record using rieMiner, the best is to join Discord to discuss about it. |
|
|
|
You can now trade RIC in SouthXchange!Thanks to everyone who contributed to the listing fee! In comparison to previous exchanges where Riecoin is listed, SouthXchange is a major one, providing more liquidity, which will likely help to stabilize the markets and increase the RIC value. But it is only a first step, and we still have a lot to do: getting listed to more exchanges, improve our software, spread our project, and more! We are as always looking for new developers!
|
|
|
|
P.S. I want to clarify - taking into account the cost of the SXCC coin of 100 Satoshi, to add to this exchange you need only $ 200 (250,000 SXCC) - if everyone pays 10 dollars, then 20 people are enough to reach this amount ...
Unfortunately, your math is off, 250000 Sxcc is actually 10 times more than $200... |
|
|
|
Now, rieMiner was involved in a third prime constellation record, as I beat the world record of prime 9-tuplets  ! The nonuplet was submitted to Tony Forbes, who confirmed its validity and listed it on his website showing the largest known prime constellations. It has 214 digits (Difficulty 709), while the previous one had 203 digits. The processor was again an AMD Ryzen 3700X @ 4 GHz and it was estimated to take about 30 days to find such nonuplet. I was this time luckier as it took instead about 15 days. If there are people interested in beating these records, they are more than welcome! |
|
|
|
I remember reading somewhere in this thread that there is a closed source miner that achieves around 20% better performance. It's porbably because of a "continue" statement instead of a "break" when verifying primes in verify_thread in riecoinMiner.cpp: https://github.com/gatra/fastrie/blob/stratum/xptMiner/xptMiner/riecoinMiner.cpp#L451This causes the miner to check the primeness of every number in the tuple, even when the tuple cannot be a valid share anymore. Since the mpz_powm operation is where most of the time is spent, this can have a significant performance impact. You are right, it should indeed be a break statement, I just fixed it in rieMiner. Good catch! This improves the performance by about 5% without having to change anything at the pool's end. However, you should no longer use the outdated Xptminer... With this, the other pooled mining issue is less affecting performance, but my suggestion of requiring that the first 2 numbers must be prime would still help making pooled mining more efficient (both issues overlap while still being distinct). None of the changes will affect Solo Mining, though. The only person that proposed a closed source miner and claimed a 20-25% improvement was someone that was hostile to the Riecoin community, and that is no longer around (Simba84/RiePool). There were no actual way to prove that the miner was actually more efficient, and this person pretended that it was rather due to some advanced Assembly optimizations... |
|
|
|
How do you set the miner to do this? ... I am quite interested. #crysx If you wish to enter the competition, below is what I wrote in #competition in Discord. If you want to take part of this competition, the important parameters in the Config file are
- Threads, BenchmarkDifficulty, ConstellationType (set how many threads you want to use to find a new record and your goal: which type of constellation and the length of the prime numbers)
- PrimeTableLimit: higher is better until a given point; the more the Difficulty, the higher the PTL should be. But with over 16 Threads or very low Difficulties, you may need to reduce this value a lot to avoid CPU Underuse
- PrimorialNumber: higher is better but the primorial must be smaller than the prime numbers you are looking for by some margin (~65 binary digits), otherwise the search will not work or loop
- PrimorialOffsets: pick numbers compatible with your Constellation Type (normally, you can simply use the first constellations' base primes)
- SieveWorkers: increase if you are affected by the CPU Underuse, lower is better
- SieveBits: higher is better; 2^SieveBits times SieveWorkers should be a number of bits that fits your L3 cache
Developers are welcomed in order to simplify the tuning by improving rieMiner (especially by definitively fixing the CPU Underuse Bug).
Currently, the easiest record to beat is still the 8-tuples. One can beat my record in about 25 days with a 3700X using a Difficulty of 1075 (my record is 1025).
The 7-tuples record can be beaten in about 50 days at Difficulty 1800 (current record is at ~1750)
For 6-tuples, it is much harder and it would take 1.5 year to find a one at Difficulty 3500 (current record is at ~3445)
For 5-tuples, it would take ~250 days to find one at Difficulty 5400 (current record is at ~5335)
Starting from 9-tuples, the CPU Underuse Bug strikes back, forcing you to use very low PTLs. It could still find a 9-tuple at Diffitculty in about 30 days at Difficulty 700 (current record is at ~675)
For 10-tuples, it would take ~40 days to find one at Difficulty 480 (current record is at ~455)
For 11-tuples, it would take ~150 days to find one at Difficulty 380 (current record is at ~360)
rieMiner is not really viable for 4-tuples and shorter and 12-tuples and longer as it would take about a decade or more to find anything...
There is a small room if you want to beat more easily records, though records by small margin will be less interesting. And of course if you have ThreadRippers or other computer beasts, you could beat records in much less time. But there is also a lot of variance so it might take much more time than estimated, or in contrary you might be lucky and find a tuple much faster than expected.
Good luck! I will add that it would be better to try to beat records that are not already owned by someone that used rieMiner, I suggest to try to beat the 9-tuples. Vidarn told me that he is trying to beat the 6-tuples record (good luck!). If many records were broken with rieMiner, it would surely attract more interest in it and Riecoin. Example of rieMiner.conf for 9-tuples that works well for me (3700X), adapt it to your system Mode = Benchmark
Threads = 16
PrimeTableLimit = 25165824
BenchmarkDifficulty = 700
Benchmark2tupleCountLimit = 0
TupleLengthMin = 8
PrimorialNumber = 89
ConstellationType = 0, 2, 4, 2, 4, 6, 2, 6, 4
PrimorialOffsets = 182403491, 226449521, 910935911, 1042090781, 1459270271, 2843348351, 6394117181, 6765896981, 8247812381, 8750853101, 11076719651, 12850665671, 17140322651, 22784826131, 24816950771, 33081664151
SieveWorkers = 10
SieveBits = 24 For example if you had a 3900X, you would use 24 Threads and probably have to lower the PrimeTableLimit (or increase the SieveWorkers) The tuning is really Trial and Error in order to get the best efficiency. The PrimorialOffsets can be filled with the numbers found here (for other tuples, just search for things like "septuplet", "octuplet",... in the website, be sure to pick the right ones) Don't discard the 8-tuples (or (k - 1)-tuples) as you can submit them as well and get easy 5th place. |
|
|
|
Very depressing times for both Riecoin and Gapcoin :| . You might try to contact Guytp to get Gapcoin listed in Zapple, and I am sure that XpoolX would gladly open a Gapcoin pool (and at the same time list the coin in XequineX). |
|
|
|
After vidarn, I just beat the world record of prime 8-tuplets using rieMiner ! The octuplet was submitted to Tony Forbes, who confirmed its validity and listed it on his website showing the largest known prime constellations. The processor was an AMD Ryzen 3700X @ 4 GHz and it was estimated to take about 17 days to find such octuplet. However the run took about 24 days. Hopefully breaking new records regularly with rieMiner will eventually attract some interest in Riecoin software and skilled developers having experience in other prime number related software! A #competition channel was opened in Discord in order to discuss about tuning or improving rieMiner to make it even more competitive for beating world records (and efficient for mining). If you are interested in taking part of this fun competition, or a developer interested in improving rieMiner, you are more than welcome to post there! Anyone with a very good CPU can participate. |
|
|
|
|
Interesting, now that you say this, FreiExchange (and Zapple) are surprisingly listed in CoinMarketCap...
Looks like they do not really enforce the "at least $1000 USD equivalent of daily trading volume" requirement after all.
Though, for the long term, it is much better to get listed in much bigger exchanges than the current ones, for example in SouthXchange, rather than risk to be delisted again from CoinMarketCap...
|
|
|
|
Thank you for info. Will share to my friends on twitter  Thank you ! You can also share about SouthXchange. They changed the voting conditions and made the threshold much easier to reach. Anyone can now vote for Riecoin more easily by buying SXCC. Every Wednesday we pick the most voted coin. Only one coin is selected. 1 vote = 1 SXCC. You can buy SXCC here. Minimum 250000 votes required to be considered. Votes are cumulative from week to week. 1 Sxcc is currently worth ~100 satoshis so in Btc it is ~0.25. Before, the minimum was 0.5 Btc. If people could donate 0.05-0.1 Btc we could be listed there soon! But small contributions like 1000 or even 100 votes are also welcome! Spread the word! We currently have 3501/250000 votes thanks to Czakris. Too bad they did not translate the 0.007 Btc to 7000 votes... Also if someone could create and manage a Twitter/Facebook Riecoin account that would be nice too. Personally I am not really into social networks... |
|
|
|
Here are more precise conditions for coins voting in C-Patex: - To vote a candidate you must have at least 10 PATS in your balance and a minimum of 0.01 BTC in trades volume
- Users having more than 100 PATS and more than 0.1 BTC trades volume can vote twice
- Users having more than 1000 PATS and more than 1 BTC in trades volume can vote three times So you need to use the exchange a bit in order to vote, it is not as straightforward as I thought. Right now, a Pats is worth about 0.0002 Btc. Otherwise you can send some Ltc to the Riecoin's voting address. Currently I cannot vote, but I invite people to vote for Riecoin if they can as having Riecoin relisted in CoinMarketCap would be great, and this exchange, while very small, has much more volume than Zapple. |
|
|
|
|
