[ANN] RoyalCoin - a new scrypt based coin

[gbrs]

I already posted it in the Dutch mining forum, I started a RYC P2Pool hosted in the Netherlands
The first three days have 0%-fee because I want to look how much resources this needs.

Stratum URL: http://ryc-pool.blockexplore.nl:9999/
Username is your RYC-address and password does not matter. You can find stats on http://ryc-pool.blockexplore.nl:9999/static/
You can always look up the current fee at: http://ryc-pool.blockexplore.nl:9999/fee

[1713558411]

1713558411

[1713558411]

1713558411

[1713558411]

1713558411

[1713558411]

1713558411

[1713558411]

1713558411

[Tommo_Aus]

Could http://tompool.org please be added to the pool list?

[micax1]

wallet is showing constantly - out of sync...

[mindruler]

wallet is showing constantly - out of sync...

The same problem here.
Wallet is not sycing.
royalcoins transfer don't get confirmations.
No blocks are found for some days.
Please fix the problem, I have coins waiting that I can't use.

Anyone else have the same problem..??

[VarDiff]

RoyalCoin just added to altcoins database
Good luck, royals.

[DrReaper]

Looks like the devs were pump and dump the project. Someone should take this coin over.

[blinkxzero]

Looks like the devs were pump and dump the project. Someone should take this coin over.

Yep... haven't heard any news on this for a while and the coin has dropped many pages. Hopefully someone picks it up again, I liked it honestly.

[yhgfhy8]

Blocks are being mined so fast due to the ridiculously low difficulty that the client can't even stay updated. 
Just like feathercoin and chinacoin and yacoin and junkcoin... What else is new in the alt coin world? Hopefully with the 480 block retarget it should get up to speed fast. It's orphan city right now.

[m0gliE]

Royalcoin Bootstrap.dat



   bootstrap.dat

bootstrap.dat allows a new Royalcoin client (not synced) to rapidly import the initial blocks from a
local file instead of slowly downloading blocks from random peers. This significantly reduces the
time it takes to get a client synced with the current blockchain.

Simply having bootstrap.dat in Royalcoin's expected data directory will make your initial block sync
much faster. The import process can be even faster if you use the -dbcache=1000 command line
parameter which uses an additional 1GB of RAM for the database index cache.

   Extracting the bootstrap.dat.xz

Regardless of your operating system, use the following steps to make use of the bootstrap.dat file:

1.   Download bootstrap.dat.xz from mirrors or torrent.
2.   Decompress the bootstrap.dat.
3.   Put it into the Royalcoin datadir. "%appdata%/royalcoin" / "~/.royalcoin"
         (This is the same folder that contains wallet.dat and the blocks folder.)
4.   Delete bootstrap.dat.old if you want to recover some storage space.

    Royalcoin Data Folder

    Linux

Code:

xz -d bootstrap.dat.xz 

Royalcoin's data directory is located in ~/.royalcoin/ by default. You can run ls -a to see
directories that start with a period. You can also search for the directory with the following
command:

Code:

find / -name wallet.dat -print 2>/dev/null 

   Mac
You can obtain xz from MacPorts or http://macpkg.sourceforge.net/.
royalcoin's data directory should be located in ~/Library/Application Support/royalcoin/.

   Windows
7Zip is a free utility that can decompress .xz files, so does the latest version of WinRAR.

Click on Start then Run (or press WinKey+R) and type:

Code:

explorer %APPDATA%\royalcoin 

royalcoin's data directory will open. "AppData" and "Application Data" are hidden by default in
Windows.

   Copy bootstrap.dat to data directory

Copy the bootstrap.dat to your data directory. Load the royalcoin client and wait for it to load the
blocks. After loading is complete, the bootstrap.dat will be renamed to bootstrap.dat.old at which
point you can choose to delete it.

Royalcoin - 4/9/2014 - 18,848 KB

GoogleD - https://drive.google.com/file/d/0Bz3NalaCIrQrQTh3Mm1qVV9rLXc
Torrent - https://drive.google.com/file/d/0Bz3NalaCIrQrUDMzSy1yUXlHckE

E-nautia Mirror - http://e-nautia.com/jon.marshall/disk/bootstrap/royalcoin/bootstrap.dat.xz
E-nautia Direct - https://e-nautia.com/disk/download.php?id=5450936

Royalcoin Donation Address: RNRTFYqpuinhnnYVG8HEX7E5AuV389Ryef

[Omega6]

I have seen that some Dev's have tried to get this coin up and running again.

I am looking into it and reading everything that I can about the history of this coin, while looking to simply revive the chain.

The question is are there still supporters out there for this coin?

It seems a shame to let a coin which had a nice initial image and look be messed up by what turned out to be a Dev who just wanted to dump coins, of which I never see the point, ever.

Anyway I am looking into it, trying to source out a blockchain.

I don't know why but the only checkpoint in the source code is at block 5, which is odd but interesting.

I have been able to buy royalcoin.net which by no surprise was going cheap and am looking to acquire the .org but might no need to as the .net should be enough.

A proper github will be created in my own and fresh download links to my SourceForge but only if there is or will be a support base for this coin?

It might be easier and I would only do this if everyone agreed but I could relaunch this coin with a fresh block chain, a fair launch of small blocks at the start slowly rising to the target block reward and not the unfair way in which this coin was release with huge block rewards at the start.

If whichever plan decides to go ahead, I would start a fresh unmoderated forum thread on here, moderated ones just look untrustworthy sometimes.

[yingxue]

i would like the coin because of some reason, and I hope the coin goes on far and far....

[Omega6]

To be honest I fear that anything that would be left of the original chain will have been 51% many times.

I cannot even find a working blockchain to run on a seednode.

If nothing turns up I will consider a reboot with a fair initial mine of lesser coins to start and 0% premine, getting Royalcoin off to a start that it deserves?

[indiguy]

RoyalCoin now on coinwik.org

RoyalCoin now has it's own page on http://coinwik.org a wikipedia listing all the alt coins to help you quickly find facts and links about your favorite coin.

http://coinwik.org/RoyalCoin

If you know of other facts and links that can be added to the page, please feel free to update the page.

[memecoin]

Royalcoin.net is the dev website according to the wiki and a few pools etc.

I have taken over the site, so I will do it up, get a proper Github working.

I have a cloud server that could act as a seednode for it aswell if that will help?

I have seen that some Dev's have tried to get this coin up and running again.

I am looking into it and reading everything that I can about the history of this coin, while looking to simply revive the chain.

The question is are there still supporters out there for this coin?

It seems a shame to let a coin which had a nice initial image and look be messed up by what turned out to be a Dev who just wanted to dump coins, of which I never see the point, ever.

Anyway I am looking into it, trying to source out a blockchain.

I don't know why but the only checkpoint in the source code is at block 5, which is odd but interesting.

I have been able to buy royalcoin.net which by no surprise was going cheap and am looking to acquire the .org but might no need to as the .net should be enough.

A proper github will be created in my own and fresh download links to my SourceForge but only if there is or will be a support base for this coin?

It might be easier and I would only do this if everyone agreed but I could relaunch this coin with a fresh block chain, a fair launch of small blocks at the start slowly rising to the target block reward and not the unfair way in which this coin was release with huge block rewards at the start.

If whichever plan decides to go ahead, I would start a fresh unmoderated forum thread on here, moderated ones just look untrustworthy sometimes.

First, one in the same?

Next, if you start this coin back up with a fresh chain, it is no longer Royalcoin.  This coin just needs a new difficulty adjustment and if (big if) interest grows, the base can be updated to the newest Litecoin source. The difficulty fix could be accomplished with little effort and would result in a healthier network.

[memecoin]

I'll take a lack of response to my previous post as a confirmation, CaptChadd/Omega6.  

This chain, like many of the early copy/paste garbage, could use a few updates.  Is there even one person who would like to see this happen?

[m0gliE]

I'll take a lack of response to my previous post as a confirmation, CaptChadd/Omega6.  

This chain, like many of the early copy/paste garbage, could use a few updates.  Is there even one person who would like to see this happen?

I would suggest to simply make adjustments to the difficulty and update the coins core along with some checkpoint updates. Nothing needs to be wiped clean, and nothing drastic needs to be done. The old original blockchain can still be used. I still also have the Royalcoin bootstrap.dat file that I created awhile back hosted on google drive.

Look at the modifications that have been made for Casinocoin, Galexycoin, Starcoin and Emerald.. I've assisted where I can and will do the same with Royalcoin. (The community offers their input, suggestions, expertise and time. I see no reason why the same can't be done for Royalcoin.

1.) Create a github source
2.) Create a block explorer
3.) Create a new thread

See if you can't stir up some interest from previous users who posted in this thread.
Find out who can be trusted to include to the git repository to make updates and modifications.

[rudy4682]

I'll take a lack of response to my previous post as a confirmation, CaptChadd/Omega6.  

This chain, like many of the early copy/paste garbage, could use a few updates.  Is there even one person who would like to see this happen?

I would suggest to simply make adjustments to the difficulty and update the coins core along with some checkpoint updates. Nothing needs to be wiped clean, and nothing drastic needs to be done. The old original blockchain can still be used. I still also have the Royalcoin bootstrap.dat file that I created awhile back hosted on google drive.

Look at the modifications that have been made for Casinocoin, Galexycoin, Starcoin and Emerald.. I've assisted where I can and will do the same with Royalcoin. (The community offers their input, suggestions, expertise and time. I see no reason why the same can't be done for Royalcoin.

1.) Create a github source
2.) Create a block explorer
3.) Create a new thread

See if you can't stir up some interest from previous users who posted in this thread.
Find out who can be trusted to include to the git repository to make updates and modifications.

I have a block explorer ready to go.
i need a valid node list, only see one node.
173.238.180.157:9556 with a starting height of 51147


http://ryc.blockexp.info     

[m0gliE]

It appears as though the chain has split, possibly an attempt to fork the chain awhile back. From what I've gathered there are currently two chains, the original legit chain from which I created the bootstrap.dat file from back in April now has 54288 blocks. The other (bad) chain has well over 584426 blocks.

A look at getpeerinfo reveals clients that have mixed subversions, all of which also have the starting height around 584426 blocks.

Code:

/DGC:2.0.0/
/WorldcoinFoundation:0.8.6.2/
/42:0.7.0/
/MemeCoin:2.2.0/

There are currently only a handfull clients, one of which is the block explorer that has the correct starting height and is also on the (correct) client version.

Code:

/Satoshi:0.6.3/

To stop your client from connecting to these rogue peers and seeing your wallet get out of sync, you need to edit your royalcoin.conf file and connect directly to the good peers. Using connect instead of addnode will prevent the other peers from connecting.

Code:

connect=50.128.154.237
connect=63.170.87.173
connect=70.164.233.141
connect=70.164.233.143
connect=173.238.180.157
connect=204.11.237.73
connect=108.172.121.86

These have the correct starting height at around 54294.

This is only a temporary fix until the client is updated.

[beitris.dwlul]

diff changes x20 each time 

[rudy4682]

It appears as though the chain has split, possibly an attempt to fork the chain awhile back. From what I've gathered there are currently two chains, the original legit chain from which I created the bootstrap.dat file from back in April now has 54288 blocks. The other (bad) chain has well over 584426 blocks.

A look at getpeerinfo reveals clients that have mixed subversions, all of which also have the starting height around 584426 blocks.

Code:

/DGC:2.0.0/
/WorldcoinFoundation:0.8.6.2/
/42:0.7.0/
/MemeCoin:2.2.0/

There are currently only a handfull clients, one of which is the block explorer that has the correct starting height and is also on the (correct) client version.

Code:

/Satoshi:0.6.3/

To stop your client from connecting to these rogue peers and seeing your wallet get out of sync, you need to edit your royalcoin.conf file and connect directly to the good peers. Using connect instead of addnode will prevent the other peers from connecting.

Code:

connect=50.128.154.237
connect=63.170.87.173
connect=70.164.233.141
connect=70.164.233.143
connect=173.238.180.157
connect=204.11.237.73
connect=108.172.121.86

These have the correct starting height at around 54294.

This is only a temporary fix until the client is updated.

it looks like Royalcoin, Worldcoin and Memecoin all use the same "peerMagic"
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Royalcoin: increase each by adding 2 to bitcoin's value.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // MemeCoin: increase each by adding 2 to bitcoin's value.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Worldcoin: increase each by adding 2 to worldcoin's value.
the peerMagic can't be changed without destroying the block chain.

The easiest fix would be to set the client/subversion name to RYC or Royal and only answer/accept other clients that have the same subversion name.
then each time a checkpoint is needed the client could be set to answer/accept other clients that have the same subversion name and build number.