gavrilo77
|
|
January 15, 2019, 03:33:27 AM |
|
Solo mining on the new release works without problem
|
|
|
|
Pon13
|
|
January 15, 2019, 07:43:39 AM |
|
yesterday, i've upgraded wallet to the latest version (rc) mined a few rics without a problem from ublock.it meaning that are shown in the new wallet normally. everything seems to work like a charm
|
Bill Hicks was right about....everything
|
|
|
clo1
Jr. Member
Offline
Activity: 35
Merit: 2
|
|
January 15, 2019, 07:04:52 PM |
|
Ah, I think I found some of your technical issues... My impression is that I don't think transaction size should be any issue for Riecoin since we will most likely never approach scaling issues like upstream. I wasn't aware of any issue with zero-fee transactions and segwit, if a miner wishes to mine them I don't see a reason why that is not allowed (that would be a pool or miner setting, correct?).
Segwit's benefits for Riecoin are beyond scaling though, Script versioning and MAST, Schnorr, others come to mind.
The issue of zero-fee transactions is independent of segwit. I don't think they are possible, but they can be set to .00000001. Here is what I wrote a couple months ago. I looked into transaction fees a a bit. I think there is enough flexibility through configuration options that we don't need to add a zero transaction fee capability. The parameters are: mintxfee - the minimum transaction fee in RIC/kB minrelaytxfee - the minimum transaction fee for a node to relay the transaction in RIC/kB blockmintxfee - minimum fee for a transaction to be included in blocks created by mining code, in RIC/kB
The defaults are all 0.00001000 RIC/kB. The smallest value is .00000001.
-mintxfee=.00000001 -minrelaytxfee=.00000001 -blockmintxfee=.00000001 will allow transactions of 1 satoshi (or gatra). I have tested this on testnet.
This way we allow users, nodes, and miners to determine what rates should be instead of fixing it in code and we stay consistent with bitcoin.
I could see possibly lowering the defaults.
Two other values that might be useful: fallbackfee - the standard fee, defaults to 0.00020000 RIC/kB m_discard_rate - any change smaller than this is considered dust and is added to the transaction fee, default is .00010000
|
|
|
|
|
xpoolx
|
|
January 18, 2019, 07:34:55 PM |
|
That blocks are for compensate the superblock.
|
|
|
|
|
PttnMe
Member
Offline
Activity: 113
Merit: 51
Riecoin developer
|
|
January 19, 2019, 01:24:07 PM Last edit: January 19, 2019, 03:51:08 PM by PttnMe |
|
I compiled rieMiner in a Toshiba AC100 (Armhf CPU, Ubuntu 16.04) without any issue, so rieMiner should work in a Raspberry Pi with Linux. Note that you need to use the Light branch. Also be sure to read properly the README.md (in particular, 32 bits compilation instructions (no longer needed) and reduce the PrimeTableLimit for less memory usage). If you need help, please post questions here. As pi64 seems to be Debian based, you should not encounter any other issue. Someone else was able to make rieMiner work on RaspBerry Pi without any issue. # apt install g++ make git libjansson-dev libcurl4-openssl-dev libssl-dev libgmp-dev git clone https://github.com/Pttn/rieMiner.git cd rieMiner git checkout Light make -j 4
Enjoy.
|
Riecoin - Mine prime constellations, not hashes, not memes! Stelo.xyz pool operator
|
|
|
Ralvsen
Newbie
Offline
Activity: 4
Merit: 0
|
|
January 20, 2019, 10:18:01 PM |
|
Enjoy.
Works. Merci. had to add to the rieMiner.conf: #256 Men in Black PrimeTableLimit = 268435456 512 MiB didn't work still states "using >1100MiB" which is funny since RPi3 only has 1024 MiB, but hey, it works... Hashrate is >340 kH/s (says my pool) Is there a chance that coinmarketcap will track RIC again? Or am i only doing Mathematics a favor now? cheers
|
|
|
|
PttnMe
Member
Offline
Activity: 113
Merit: 51
Riecoin developer
|
|
January 22, 2019, 11:47:38 AM |
|
Works. Merci. had to add to the rieMiner.conf: #256 Men in Black PrimeTableLimit = 268435456 512 MiB didn't work still states "using >1100MiB" which is funny since RPi3 only has 1024 MiB, but hey, it works... Hashrate is >340 kH/s (says my pool) Glad to hear that, I wonder how much RIC/day you are earning. At least the RaspBerry Pi uses very low power. The memory estimation is not really accurate for now, especially for lower amounts, it just gives a rough estimation. I opened an issue about that if someone is interested in improving this. Anyone wanting to contribute to rieMiner can read its issues. If new features are wanted, one can also open another issue. Is there a chance that coinmarketcap will track RIC again? Or am i only doing Mathematics a favor now? They might consider tracking again if Zapple's daily volume for RIC/BTC ever reaches $1000 equivalent like asked in their Request Form. Zapple will only start advertising on Summer once they are ready, we can only hope that they will find a place in the competition, or that we get listed in another important exchange. Else not much is happening in our community sadly. Some social activity like Medium articles or posts/comments in CPU mineable coins compilations are welcome. Or someone can try to break any tuple world record with the rieMiner's Benchmark Mode.
|
Riecoin - Mine prime constellations, not hashes, not memes! Stelo.xyz pool operator
|
|
|
Ralvsen
Newbie
Offline
Activity: 4
Merit: 0
|
|
January 23, 2019, 06:22:38 PM |
|
Glad to hear that, I wonder how much RIC/day you are earning. At least the RaspBerry Pi uses very low power.
..and is pretty silent - i am not having a lot of experience since i only started recently mining RIC with Pi, but it looks like its something like 1(one) coin/day maybe i should do a YT, so i can show it to my students cheers
|
|
|
|
|
cryptapus
|
|
January 25, 2019, 02:00:44 PM |
|
...
In addition, I flashed a PR to riecoin on github to notify gatra that a release has been made. clo1 can decide if an upstream PR is necessary (it would be nice if clo1 did get the offered bounty). https://github.com/riecoin/riecoin/pull/10
|
website | PGP fingerprint: 692C 0756 E57D 2FA1 7601 3729 010B 717F 231C E7AA | BTC Address: 1CrYPTB1o7QWc8hXqBMP2LtAJh1VMtTFBh
|
|
|
clo1
Jr. Member
Offline
Activity: 35
Merit: 2
|
|
January 25, 2019, 09:45:41 PM |
|
Major new version
Binaries and source code:
Thanks for your help with this release.
|
|
|
|
H90E86
Newbie
Offline
Activity: 2
Merit: 0
|
|
January 26, 2019, 06:14:46 PM |
|
I am seeing outgoing traffic on port 8333 and 28333 from this new client.
I thought RieCoin only communicated on port 28333.
Have I been making an incorrect assumption?
|
|
|
|
cryptapus
|
|
January 26, 2019, 11:29:40 PM Last edit: January 27, 2019, 12:01:04 AM by cryptapus |
|
I am seeing outgoing traffic on port 8333 and 28333 from this new client.
I thought RieCoin only communicated on port 28333.
Have I been making an incorrect assumption?
Port 28333 is the correct p2p port. Interesting that you're seeing some traffic on port 8333... Would you be willing to show some debug.log snippets to examine? It's possible we've missed some upstream port definitions but I don't immediately see where... (bitcoind is using port 8333) Edit: I should also add that I'm not sure v0.10.2 had all the correct ports defined... You may want to remove your peers.dat file and try a restart.
|
website | PGP fingerprint: 692C 0756 E57D 2FA1 7601 3729 010B 717F 231C E7AA | BTC Address: 1CrYPTB1o7QWc8hXqBMP2LtAJh1VMtTFBh
|
|
|
H90E86
Newbie
Offline
Activity: 2
Merit: 0
|
|
January 27, 2019, 03:47:36 AM |
|
Edit: I should also add that I'm not sure v0.10.2 had all the correct ports defined... You may want to remove your peers.dat file and try a restart.
You are right about the peers.dat file. I found a script online and dumped the contents of the peers.dat file. All of the outbound traffic on port 8333 matched entries in this file. I will follow your guidance and remove the file. Cheers!
|
|
|
|
Pon13
|
|
January 28, 2019, 07:34:42 AM |
|
Major new version
Binaries and source code:
Thanks for your help with this release. Good job and many thanks to all involved in this upgrade !! Let's hope Gatra is around to give bounty to clo1
|
Bill Hicks was right about....everything
|
|
|
gavrilo77
|
|
February 14, 2019, 06:02:10 AM |
|
Someone knows what are the future plans?
|
|
|
|
cryptapus
|
|
February 14, 2019, 06:29:39 PM |
|
Just to note that I'm observing (via getblockchaininfo) >10% of blocks are now signalling CSV/Segwit. That's a bit of progress from the last few weeks. If you're a miner and wish to try out the new version at https://github.com/riecointeam/riecoin/releases/tag/v0.16.3.0 your feedback is welcome.
|
website | PGP fingerprint: 692C 0756 E57D 2FA1 7601 3729 010B 717F 231C E7AA | BTC Address: 1CrYPTB1o7QWc8hXqBMP2LtAJh1VMtTFBh
|
|
|
PttnMe
Member
Offline
Activity: 113
Merit: 51
Riecoin developer
|
|
February 15, 2019, 12:13:14 PM |
|
Someone knows what are the future plans?
Besides softforks there are some discussions in Discord of improving the Riecoin proof of work to not be stuck with only 6-tuples (there would be a hardfork for that like there was for the SuperBlocks). It looks like that it is due to RGsGkJpmb4eQATbskACNW1Azyumxp1PbTt upgrading. Thank you whoever you are for upgrading. XpoolX upgraded since long too. Unfortunately none from All Others/RSoTqU.../RLGzid.../RG6ZoZ.../RiePool/GpuPool/Ublock.it upgraded... Please everyone upgrade to make 0.10.2 a thing of the past and fully benefit from the new features.
|
Riecoin - Mine prime constellations, not hashes, not memes! Stelo.xyz pool operator
|
|
|
|