I had not heard about the 2106 time stamp problem before, so had to look it up  So apparently timestamps in bitcoin only run until 2106 unless a hardfork will be made. Is this problem general in cryptocurrency or only for bitcoin/darkcoin ? What I mean to ask: Is there any other coin that is addressing this problem and that already has this 64 bit timestamp fix? Probably it's not a big problem and I'm sure Bitcoin devs will be able to handle it if time will come, though they will need to put some effort in it. AFAIK most Bitcoin forks are affected by this issue and I don't know about any other fork which fixes it. Meanwhile, I added checkpoint into wallet, you can download new version from OP. Also, I tried to make 64-bit Windows build (mining should be faster with 64 build), I made some fixes for it but it still fails with some strange linking errors. |
|
|
|
Fixed, I added this Makefile (it wasn't added in the initial commit because it was listed in gitignore). I am very curious to hear your plans for further development DEV  My immediate plans are: 1. Set up a DNS seed. Currently it uses open BitTorrent trackers for peer discovery but I feel it uncomfortably to rely on 3-rd party services. 2. Make better logo and new splash screen. I'm not a designer myself but I have someone to ask. 3. Make block explorer inside the client. I already have some working code but it is yet incomplete. 4. Make online block explorer. As for the more distant future, I have many great ideas. Many of them will probably be to difficult to implement but I still want to make something special for this coin. |
|
|
|
This should be fun... block reward 66.66666666? Maybe you should have just went with 666. No plan, just do a coin for fun called "SpreadCoin".. As in bend over, spread wide and take it deep? lol
The point is to make supply similar to Bitcoin but without abrupt reward halvings. Now it is 66.66666666, in two years it will be 50 and in four years 33.33333333. So that reward will halve in 4 years and supply in the first 4 years will be almost the same as in Bitcoin but without abrupt halvings. Yeah, looked at some of the source and it mentions DarkSend which I thought was a Darkcoin thing.. and some of the other comments in there seem to indicate it's X11 as well.
Yes, there is DarkSend in the source code but it is currently disabled (beacuse it is still not yet fully implemented in Darkcoin). In the future it may be enabled with hardfork. |
|
|
|
|
Block header was changed in this coin: time value was changed from 32 bits to 64 (to fix year 2106 problem) and block height was added (to make it easier to add extensions later). This is probably the reason why X11 miners don't work, they were optimized for hashing data of some specific size and they can't work with other header sizes while internal miner uses built-in X11 implementation which can hash data of arbitrary size. It is possible to fix external miners but it may be non-trivial. For now you can only mine with built-in miner.
|
|
|
|
|
Algorithm is X11, I tried external CPU miner and it didn't work for me. I'm still trying to find what is the reason.
But I can say for sure that it isn't X13!
|
|
|
|
|
Are you using some external miners? I didn't test it but it should work because I didn't change mining algo. I'm mining with built-in miner.
|
|
|
|
sorry ,all reject ,
so dev ,you play yourself.
You still can't connect to the network? I have 23 connections, I don't know why it doesn't work for you. How do you add nodes? You can use for example "addnode 61.251.187.134:41678 add" in console. |
|
|
|
can not link to net
Here are some nodes. You can add them manually just change port to 41678. [
{
"addr" : "222.117.16.10:62225",
"services" : "00000003",
"lastsend" : 1406625099,
"lastrecv" : 1406625099,
"bytessent" : 40565,
"bytesrecv" : 21182,
"blocksrequested" : 150,
"conntime" : 1406624447,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "61.251.187.134:2832",
"services" : "00000003",
"lastsend" : 1406625098,
"lastrecv" : 1406625098,
"bytessent" : 40021,
"bytesrecv" : 18712,
"blocksrequested" : 150,
"conntime" : 1406624554,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 8,
"banscore" : 0
},
{
"addr" : "218.86.136.232:54393",
"services" : "00000003",
"lastsend" : 1406625099,
"lastrecv" : 1406625098,
"bytessent" : 36123,
"bytesrecv" : 23889,
"blocksrequested" : 127,
"conntime" : 1406624564,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 5,
"banscore" : 0
},
{
"addr" : "86.198.249.138:41678",
"services" : "00000003",
"lastsend" : 1406625098,
"lastrecv" : 1406624771,
"bytessent" : 10424,
"bytesrecv" : 1819,
"blocksrequested" : 9,
"conntime" : 1406624729,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : false,
"startingheight" : 20,
"banscore" : 0
},
{
"addr" : "61.251.187.134:1328",
"services" : "00000003",
"lastsend" : 1406625098,
"lastrecv" : 1406625098,
"bytessent" : 39399,
"bytesrecv" : 19423,
"blocksrequested" : 147,
"conntime" : 1406624816,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "79.158.8.38:49240",
"services" : "00000003",
"lastsend" : 1406625098,
"lastrecv" : 1406625058,
"bytessent" : 34484,
"bytesrecv" : 12318,
"blocksrequested" : 128,
"conntime" : 1406624879,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "61.251.187.134:1440",
"services" : "00000003",
"lastsend" : 1406625098,
"lastrecv" : 1406625098,
"bytessent" : 37979,
"bytesrecv" : 15524,
"blocksrequested" : 145,
"conntime" : 1406624880,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "61.251.187.134:1463",
"services" : "00000003",
"lastsend" : 1406625098,
"lastrecv" : 1406625098,
"bytessent" : 39592,
"bytesrecv" : 14486,
"blocksrequested" : 154,
"conntime" : 1406624887,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "61.251.187.134:1529",
"services" : "00000003",
"lastsend" : 1406625099,
"lastrecv" : 1406625100,
"bytessent" : 38375,
"bytesrecv" : 13281,
"blocksrequested" : 150,
"conntime" : 1406624924,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "61.251.187.134:1734",
"services" : "00000003",
"lastsend" : 1406625098,
"lastrecv" : 1406625098,
"bytessent" : 37355,
"bytesrecv" : 9229,
"blocksrequested" : 151,
"conntime" : 1406625011,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "218.86.193.130:52339",
"services" : "00000003",
"lastsend" : 1406625099,
"lastrecv" : 1406625099,
"bytessent" : 36651,
"bytesrecv" : 7722,
"blocksrequested" : 151,
"conntime" : 1406625055,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "61.251.187.134:1841",
"services" : "00000003",
"lastsend" : 1406625099,
"lastrecv" : 1406625099,
"bytessent" : 36859,
"bytesrecv" : 8646,
"blocksrequested" : 151,
"conntime" : 1406625057,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "218.86.136.232:55249",
"services" : "00000003",
"lastsend" : 1406625099,
"lastrecv" : 1406625099,
"bytessent" : 34485,
"bytesrecv" : 18613,
"blocksrequested" : 130,
"conntime" : 1406625057,
"version" : 70018,
"subver" : "/Satoshi:0.9.11.6/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
}
] |
|
|
|
Anything new or exciting about this coin?
I have plans to improve it in the future but nothing particular is yet implemented. Currently there are just some small improvements like fixed year 2106 problem. |
|
|
|
Launch! Source codeSource code updated with proper timestamp. Windows walletPassword: vJ7dNe5AJb34LoxcvDTB12 Come on guys, it's gonna be a great coin! EDIT: Just like in many other coins you can launch debug console and enter to start mining |
|
|
|
why x11 ? Change to x15
What's wrong with X11? |
|
|
|
SpreadCoin is a new cryptocurrency which is more decentralized than Bitcoin. It prevents centralization of hashing power in pools, which is one of the main concerns of Bitcoin security. SpreadCoin was fairly launched with no premine. Pool PreventionTo prevent pools each block must be signed with the private key which correspondents to the coinbase transaction. See whitepaper for more details. Parameters- Algorithm: SpreadX11
- Block generation: 1 minute
- Difficulty retargets: every block based on last 360 blocks
- Reward starts at approx. 6.66 coins per block
- Block reward is smoothly halved every 4 years
- Total supply: 20 mln coins
- No year 2106 problem
Initial reward was 66.66 coins per block and spacing between blocks was 10 minutes, this was changed after hardfork at block 2200. Download (version 0.9.15.4, released January 24, 2015)Windows wallet (32-bit)Windows wallet (64-bit)Linux wallet (32-bit)Linux wallet (64-bit)Mac OS X walletSource codeWhite PaperDownloadExchangesBittrex
C-CEX
AllCrypt
AlcurExYou can also help us to add SpreadCoin to other exchanges by voting: BTERAskCoinBlockchain ExplorersOfficialAt MultiFaucetHashrate distribution chartServicesFaucetCasinoTranslationsChineseDutchFrenchHebrewHindiIndonesianItalianPortugueseRomanianRussianSpanishTurkishTruly DecentralizedIn Bitcoin mining power is concentrated in large pools. This puts the whole network at risk in case these pools will become malicious or if their security will be compromised. In SpreadCoin there are no pools, mining power is spread around many solo miners. Compact TransactionsSpreadCoin uses more compact representation for signatures in transactions. This leads to smaller transactions and, hence, smaller blockchain. See e.g. this transaction in SpreadCoin and similar transaction in Bitcoin, both transactions have 15 inputs and 1 output but SpreadCoin transaction takes 1661 bytes while Bitcoin one takes 2744. See this thread for more info: https://bitcointalk.org/?topic=6430.0%29%3FSmooth Reward DecreaseUnlike Bitcoin, there are no abrupt reward halvings in SpreadCoin. Block reward is smoothly decreasing over time.  MiningYou can mine directly from the wallet, just go to the mining tab and press 'Start mining', you will start mine to your wallet. Thread about mining SpreadCoin: https://bitcointalk.org/index.php?topic=869289Also you can mine to a specific address (this is useful if you are mining on several computers). To do so: 1. Use existing or better generate a new address. 2. Open debug console (Tools -> Debug Console) and enter: dumpprivkey SYourSpreadCoinAddress 3. You will get your private key. Then open spreadcoin.conf or create it if it doesn't exist (D:\Users\<username>\AppData\Roaming\SpreadCoin\spreadcoin.conf on Windows) and add the following line: miningprivkey=YourPrivateKey 4. Restart your wallet if it was running. In the Mining tab you will now see notification that all mined coins will go to this address. Mining GuideWindows: https://github.com/spreadcoin-project/SpreadCoin-Wiki/wiki/Mining-GuideBy default you can mine only from 4 machines to the same wallet, to increase this limit set rpcthreads to value greater than 4 in spreadcoin.conf. AMD GPU MinerWindows binary: http://spreadcoin.net/files/Spread-GPU-miner.7zSource code: https://github.com/spreadcoin-project/spreadcoinx11-sgminerDon't forget to read included readme, it describes how to launch it. Even if you did solo-mining before it is still worth reading. You need latest drivers to use this miner. Known to work on 14.9 installed from file named amd-catalyst-14-9-win7-win8.1-64bit-dd-ccc-whql.exe from http://support.amd.com/en-us/download/desktop?os=Windows%207%20-%2064Nvidia GPU Miner |
|
|
|
|
Show Posts
