Of the address you're talking about (5% fee to another address) there is another that has very similar behavior.
If you don't mind saving me the time, which one?
Topic: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record - page 80. (Read 685265 times)
March 09, 2017, 05:11:09 PM
Of the address you're talking about (5% fee to another address) there is another that has very similar behavior.
If you don't mind saving me the time, which one?
March 09, 2017, 12:30:59 PM
Have you seen the extraction of the blocks on blockchain?
Take 2 calculations... where is 25% of the blocks?
Take 2 calculations... where is 25% of the blocks?
Wow, that's fascinating.
https://chainz.cryptoid.info/ric/extraction.dws?1051620.htm
........................
Of the address you're talking about (5% fee to another address) there is another that has very similar behavior.
March 09, 2017, 11:41:40 AM
Have you seen the extraction of the blocks on blockchain?
Take 2 calculations... where is 25% of the blocks?
Take 2 calculations... where is 25% of the blocks?
Wow, that's fascinating.
https://chainz.cryptoid.info/ric/extraction.dws?1051620.htm
Address appeared around block 500,000. Has mined 26,658 blocks. It's not associated with one of the identified pools, unless I'm misunderstanding something about the interface.
Sends most of its money to PoloniEx at RNNHdqNDractqtCwZK65xU7FJaH1ZsY2yw . That address has received 433,583 RIC.
Appears to be paying 2.5 RIC per block - perhaps a miner fee - to RR1eWm6tPdD6fEXtkZYEivGihSL6WwU8CH .
Those payments get bundled up and sent to Poloniex at RAf64oRWepwcpeQG7dSMDjpy3P31fBzR5C .
The amount extracted by this set is highly time-variable -- probably a botnet, not a farm, with a herder who paid someone to either craft a custom miner for them or create a "stealthed" miner. Many other possible explanations, of course -- a private optimized miner, or someone stealing their local supercomputer to mine RIC -- but that seems like the most likely.
(Edited to add: Oh, duh - the fee is probably for someone running a private pool for them.)
Maybe I need to do another "exploring the Riecoin blockchain" blog post. I need more hours in the day during the semester, this sounds fun.
March 09, 2017, 01:22:14 AM
Have you seen the extraction of the blocks on blockchain?
Take 2 calculations... where is 25% of the blocks?
Take 2 calculations... where is 25% of the blocks?
March 08, 2017, 03:50:31 AM
There's a tweak for periodic "high diff" blocks to set the record primes, and I don't know that part of it.
It would be nice to assemble these all, now that you mention it.
It would be nice to assemble these all, now that you mention it.
Once per week we have a block that has a target of 2hs instead of 2.5mins. So for that block we have a higher difficulty, which was enough to break the record a couple of times. The harder block also has more reward, and for the next blocks after the superblock the reward and target times are a tiny bit smaller than usual. This compensates for the superblock and keeps the average supply and block rates at their originally intended values.
With the new upcoming update I'm hoping to have a new website with all the info put together in a friendlier way.
that would be awesome ...
if there is any help we can give here - let us know ...
what we can afford to do - we will ...
#crysx
Running a DDoS-protected node would be a great first step. I've got two online now, ziiip already has several. A few more and it will be substantially more difficult to split the network.
I've paid for my two for a year in advance, so hopefully by then we'll have a bigger ecosystem.
I'll see if I can find a third cheap DDoS-protected hoster this weekend, and call that a day.we can have a look sometime soon ...
if we can get it compiled in our test node - then we can do a bit more with it ...
#crysx
March 07, 2017, 01:30:48 PM
yup - it would be ...
and a name for the algo it uses - or have a missed that? ...
...
and tanx - that is so much better than looking for it all in various places - especially since this IS the thread for it ...
i really appreciate that ... off to bed for me now ...
#crysx
and a name for the algo it uses - or have a missed that? ...
...and tanx - that is so much better than looking for it all in various places - especially since this IS the thread for it ...
i really appreciate that ... off to bed for me now ...
#crysx
I don't think it has a name - I've always just thought of it as the Riecoin PoW. To my knowledge, Gatra invented it and it's not been used in this specific form before or since. (Which is both nice - since it means there's one place to focus mining for finding huge prime clusters - and also a bit of a shame, since it's a fun one.)
There are some other prime-based currencies, but I don't think any have the same combination of maximally dense 6-tuples, and increasing difficulty by making the numbers larger. Primecoin, for example, increased diff by finding longer chains, and used Cunningham chains, not dense 6-tuples.
I could suggest some names if you needed, but I think that's really for Gatra to do.
Another coin that is in some way similar to Riecoin is Nexus (NXS), which also searches for dense k-tuples for relatively big numbers (1024bit), but like in Primecoin the difficulty is controlled by the chain length and the Fermat reminder.
March 07, 2017, 12:10:27 PM
There's a tweak for periodic "high diff" blocks to set the record primes, and I don't know that part of it.
It would be nice to assemble these all, now that you mention it.
It would be nice to assemble these all, now that you mention it.
Once per week we have a block that has a target of 2hs instead of 2.5mins. So for that block we have a higher difficulty, which was enough to break the record a couple of times. The harder block also has more reward, and for the next blocks after the superblock the reward and target times are a tiny bit smaller than usual. This compensates for the superblock and keeps the average supply and block rates at their originally intended values.
With the new upcoming update I'm hoping to have a new website with all the info put together in a friendlier way.
that would be awesome ...
if there is any help we can give here - let us know ...
what we can afford to do - we will ...
#crysx
Running a DDoS-protected node would be a great first step. I've got two online now, ziiip already has several. A few more and it will be substantially more difficult to split the network.
I've paid for my two for a year in advance, so hopefully by then we'll have a bigger ecosystem.
I'll see if I can find a third cheap DDoS-protected hoster this weekend, and call that a day. March 06, 2017, 07:29:06 PM
There's a tweak for periodic "high diff" blocks to set the record primes, and I don't know that part of it.
It would be nice to assemble these all, now that you mention it.
It would be nice to assemble these all, now that you mention it.
Once per week we have a block that has a target of 2hs instead of 2.5mins. So for that block we have a higher difficulty, which was enough to break the record a couple of times. The harder block also has more reward, and for the next blocks after the superblock the reward and target times are a tiny bit smaller than usual. This compensates for the superblock and keeps the average supply and block rates at their originally intended values.
With the new upcoming update I'm hoping to have a new website with all the info put together in a friendlier way.
that would be awesome ...
if there is any help we can give here - let us know ...
what we can afford to do - we will ...
#crysx
March 06, 2017, 02:54:34 PM
There's a tweak for periodic "high diff" blocks to set the record primes, and I don't know that part of it.
It would be nice to assemble these all, now that you mention it.
It would be nice to assemble these all, now that you mention it.
Once per week we have a block that has a target of 2hs instead of 2.5mins. So for that block we have a higher difficulty, which was enough to break the record a couple of times. The harder block also has more reward, and for the next blocks after the superblock the reward and target times are a tiny bit smaller than usual. This compensates for the superblock and keeps the average supply and block rates at their originally intended values.
With the new upcoming update I'm hoping to have a new website with all the info put together in a friendlier way.
What version are we moving to on the update?
March 06, 2017, 12:57:29 PM
There's a tweak for periodic "high diff" blocks to set the record primes, and I don't know that part of it.
It would be nice to assemble these all, now that you mention it.
It would be nice to assemble these all, now that you mention it.
Once per week we have a block that has a target of 2hs instead of 2.5mins. So for that block we have a higher difficulty, which was enough to break the record a couple of times. The harder block also has more reward, and for the next blocks after the superblock the reward and target times are a tiny bit smaller than usual. This compensates for the superblock and keeps the average supply and block rates at their originally intended values.
With the new upcoming update I'm hoping to have a new website with all the info put together in a friendlier way.
March 06, 2017, 01:40:27 AM
Those 300 connections are not good, I'm putting together a block list. White-listing inbound connections is great for keeping your node up and preventing DDoS but what about people who need to download the chain? Some nodes still need to be listening.
nodes ...
if i can get a static compile in the nodes we currently have - ill setup 1 for testing purposes ...
these will not be plain wallets - these are FULL nodes to service the network ...
being centos 7 x64 - these are not as easy to compile as most think ... so ill have to rewrite the compile scripts for it - but should be ready as soon as i have some time to allocate to it ...
so ill work on it when i can ... and if it tests well ( we need to get coins in each of the nodes ) we will look at the how when where and why of getting a few more done ...
the more i look into this coin and tech - the more interested i get ...
though not everything is fully organized yet - such as the consolidation of all info into one page / op ... but i understand that - as we are in the same situation of ( dis ) organization also ...
#crysx
March 06, 2017, 01:10:28 AM
Those 300 connections are not good, I'm putting together a block list. White-listing inbound connections is great for keeping your node up and preventing DDoS but what about people who need to download the chain? Some nodes still need to be listening.
March 06, 2017, 01:04:49 AM
Someone is now saturating all connections on some nodes, So I just spun up a few more with 1000+ connection slots.
I've been running several VPS nodes for a few months now trying to keep this network alive. Initially it was to resolve the forking issues, now i'm just helping out the network. Anyone who can spin up more nodes would be greatly appreciated!

{
"version" : 100200,
"protocolversion" : 10070001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 633965,
"timeoffset" : 0,
"connections" : 334,
"proxy" : "",
"difficulty" : 1399.00000000,
"testnet" : false,
"keypoololdest" : 1486796207,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
I've been running several VPS nodes for a few months now trying to keep this network alive. Initially it was to resolve the forking issues, now i'm just helping out the network. Anyone who can spin up more nodes would be greatly appreciated!

{
"version" : 100200,
"protocolversion" : 10070001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 633965,
"timeoffset" : 0,
"connections" : 334,
"proxy" : "",
"difficulty" : 1399.00000000,
"testnet" : false,
"keypoololdest" : 1486796207,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
my research is always for the future ...
granite has 25hardcoded seednodes - making syncing and new connections a breeze with no 'fiddling' with conf files and searching for nodes to add ( addnodes ) ... we will be growing this to a much larger number this year ( aiming at 70 by the end of the year ) - and as such - the cwi-ecosystem supports a number of coins currently - not just 'our' coins ...
as such - we have been looking at this coin purel on a technical level for two reasons ...
1 - what it does and how ( if we do ) to support it ...
2 - whether it would be a viable addition to the small list of coins we support currently ...
it seems that it is positive on both counts here - and so we will look more indepth at not only seednodes - but also the support when the cwi-website is up and fully functional ...
as always with us at cwi - we take things slow and steady ( like our growth ) and make sure of the things we like to get involved in ...
im personally very interested in riecoin ... so will see how we go ...
but at over 300 connections so far - seems like the network is rock solid ...
...#crysx
March 05, 2017, 10:37:02 PM
Someone is now saturating all connections on some nodes, So I just spun up a few more with 1000+ connection slots.
I've been running several VPS nodes for a few months now trying to keep this network alive. Initially it was to resolve the forking issues, now i'm just helping out the network. Anyone who can spin up more nodes would be greatly appreciated!

{
"version" : 100200,
"protocolversion" : 10070001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 633965,
"timeoffset" : 0,
"connections" : 334,
"proxy" : "",
"difficulty" : 1399.00000000,
"testnet" : false,
"keypoololdest" : 1486796207,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
I've been running several VPS nodes for a few months now trying to keep this network alive. Initially it was to resolve the forking issues, now i'm just helping out the network. Anyone who can spin up more nodes would be greatly appreciated!

{
"version" : 100200,
"protocolversion" : 10070001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 633965,
"timeoffset" : 0,
"connections" : 334,
"proxy" : "",
"difficulty" : 1399.00000000,
"testnet" : false,
"keypoololdest" : 1486796207,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
March 05, 2017, 09:52:11 PM
I've seen the name primesr in reference to Riecoin before, not sure if that's correct though.
ooh. Excellent point - that's from Gatra's fork of the cpu-miner.
cpu-miner.c: [ALGO_RIECOIN] = "primesr"
You win the cookie tonight.
Thanks for the head bop about Simba running a pool. I tried to wade through some of the back pages since I stopped following the thread, but couldn't quite get through all the finger pointing. sigh.
March 05, 2017, 09:16:56 PM
I've seen the name primesr in reference to Riecoin before, not sure if that's correct though.
March 05, 2017, 09:06:09 PM
yup - it would be ...
and a name for the algo it uses - or have a missed that? ... ...
and tanx - that is so much better than looking for it all in various places - especially since this IS the thread for it ...
i really appreciate that ... off to bed for me now ...
#crysx
and a name for the algo it uses - or have a missed that? ...
...and tanx - that is so much better than looking for it all in various places - especially since this IS the thread for it ...
i really appreciate that ... off to bed for me now ...
#crysx
I don't think it has a name - I've always just thought of it as the Riecoin PoW. To my knowledge, Gatra invented it and it's not been used in this specific form before or since. (Which is both nice - since it means there's one place to focus mining for finding huge prime clusters - and also a bit of a shame, since it's a fun one.)
There are some other prime-based currencies, but I don't think any have the same combination of maximally dense 6-tuples, and increasing difficulty by making the numbers larger. Primecoin, for example, increased diff by finding longer chains, and used Cunningham chains, not dense 6-tuples.
I could suggest some names if you needed, but I think that's really for Gatra to do.
March 05, 2017, 08:05:55 PM
Anyone can connect to nodes with the wallet?
I tried with these indicated on blockchain...
addnode=107.191.63.8
addnode=112.78.46.121
addnode=116.90.234.18
addnode=137.63.131.2
addnode=192.95.24.114
addnode=206.130.99.221
addnode=207.172.128.231
addnode=5.9.39.9
addnode=98.21.31.49
None of these connects
I tried with these indicated on blockchain...
addnode=107.191.63.8
addnode=112.78.46.121
addnode=116.90.234.18
addnode=137.63.131.2
addnode=192.95.24.114
addnode=206.130.99.221
addnode=207.172.128.231
addnode=5.9.39.9
addnode=98.21.31.49
None of these connects
Try 172.94.61.249
But be warned - you might get DoS'd.
I haven't tried it yet, but you might try using the --connect=
flag to tell your node *only* to connect to mine, just to see if it lets you avoid the DoS, if you have a problem with it.
one of the reasons i ask so many questions ...
all good though - so far im impressed with the coin ... we might be able to help out here ...
#crysx
March 05, 2017, 07:42:21 PM
Simba knows full well about the DDoS attacks, not to mention he's running a functional pool. Simba, if you've been trying to connect to my node with some bogus version string, you're likely blocked
dga, if you've been getting DDoS'd I'm sure Simba has white-listed you now. Thanks Simba!
dga, if you've been getting DDoS'd I'm sure Simba has white-listed you now. Thanks Simba!
March 05, 2017, 01:45:12 PM
Anyone can connect to nodes with the wallet?
I tried with these indicated on blockchain...
addnode=107.191.63.8
addnode=112.78.46.121
addnode=116.90.234.18
addnode=137.63.131.2
addnode=192.95.24.114
addnode=206.130.99.221
addnode=207.172.128.231
addnode=5.9.39.9
addnode=98.21.31.49
None of these connects
I tried with these indicated on blockchain...
addnode=107.191.63.8
addnode=112.78.46.121
addnode=116.90.234.18
addnode=137.63.131.2
addnode=192.95.24.114
addnode=206.130.99.221
addnode=207.172.128.231
addnode=5.9.39.9
addnode=98.21.31.49
None of these connects
Try 172.94.61.249
But be warned - you might get DoS'd.
I haven't tried it yet, but you might try using the --connect=
flag to tell your node *only* to connect to mine, just to see if it lets you avoid the DoS, if you have a problem with it.
Jump to: