I'd go so far as to recommend the development of some sort of technical education programme focused on the coin and its features.
Already working on it. It will be called "Spread the knowledge""brought to you by Spreadcoin"Stay tuned for more. |
|
|
|
I got my Satoshi van gen  Can I suggest that every service node starts with "Satoshi......" to be valid. This will make sure that everyone tries out the new Van Gen  Actually, I think we should make this an enforcement as a way to stop some people flooding the network with farms of nodes. It takes about 10 hrs to get a Satoshi address. So there are only so many nodes you can create overnight. Any views? hehe, nice idea! Maybe we can ask servicenodes to create a special vanity address for every 30% payment they'll get, lol. Maybe addresses starting with SayThankYou... or SayThanks... Anyway, this can be a valid way of occupying the CPU for a while (for whatever reason). Damn, why don't I have a Satoshi - address yet. I will have to beat you by creating a SatoshiN - address, but I can't really let my computers run at full speed because the whole room is already cooking with those record heat summer days.  |
|
|
|
Downloading now. Thanks georgem!
Thank you for testing. Please let me know first if it even works and what MacOsX version you are using. You can do a more thorough testing later. I quickly tested it on 10.7.5 and it works. |
|
|
|
Been playing with the wallet. Can't really find any bugs. I'm sure there is the odd one, so I'll keep playing. Who is AWOLAND that is updating Spreadcoin's github? https://github.com/awoland?tab=activityLook like good contributions. But who has access to the repo? he's an early legendary forum member that has been around since 2012. https://bitcointalk.org/index.php?action=profile;u=63082I have no problem with the update he made on github (it's just a small change in the qt wallet, that will show the datetime with seconds), it's just weird he didn't communicate with us before doing so. wait, .... if you look at his posts, they are mainly in russian language.... so that's probably the reason why... lol https://bitcointalk.org/index.php?action=profile;u=63082;sa=showPosts let's see how we are going to handle this communication barrier. There even seems to be an active russian spreadcoin subforum here at BCT: https://bitcointalk.org/index.php?topic=818442We need to reach out to those guys. I will mention their subforum in the threadstart. (but wait, their thread still talks about the old website etc... and has dead links.... so we need to fix this first) |
|
|
|
sourcecode ( git ) ? ...
edit - looks great georgem ... no block source - but ill fix that in a minute ...
work well done so far ...
#crysx
I will release the sourcecode as soon as I have the mac wallet ready. I need to clean the code up a little bit. Blocksource should be available if you just wait 30 - 60 sec, then it will start accessing the backup nodes. Kudos I usually run Windows, but I'll try to spin up Linux to do some testing. Thanks, the new wallet really needs some thorough testing. |
|
|
|
Nice update Satoshi estimated to take ~15hrs on windows, with 2 cores; but only a few hours on linux with 1 core  No this was just because of the specific moment I made the screenshot. One second later it said about 20 hours. It's how vanitygen makes an estimation. Takes it a few seconds to get a good average value. It goes like: "this is so easy.... no ... wait...."  |
|
|
|
Linux 64bit version of preview wallet is ready: http://www.spreadcoin.info/downloads/preview_wallet_0.tar.xzHere are some screenshots:    A few things are slightly different between linux and windows, but never have the wallets looked so similar over multiple OSes. Please help with the testing, I appreciate it. I also appreciate donations! Stay tuned. |
|
|
|
people can now also easily share their vanitygen worklists... This is what I call the "golden" pattern list: Looking for Servicenodes and SatoshiNakamoto and spitting out partial solutions. {
"state": {
"running": "true",
"threads": "1",
"matchCase": "true",
"showPrivKeys": "true",
"autoImport": "true"
},
"workList": [
{"pattern": "Satoshi", "pubkey": "", "privkey": ""},
{"pattern": "SatoshiN", "pubkey": "", "privkey": ""},
{"pattern": "SatoshiNa", "pubkey": "", "privkey": ""},
{"pattern": "SatoshiNak", "pubkey": "", "privkey": ""},
{"pattern": "SatoshiNaka", "pubkey": "", "privkey": ""},
{"pattern": "SatoshiNakam", "pubkey": "", "privkey": ""},
{"pattern": "SatoshiNakamo", "pubkey": "", "privkey": ""},
{"pattern": "SatoshiNakamot", "pubkey": "", "privkey": ""},
{"pattern": "SatoshiNakamoto", "pubkey": "", "privkey": ""},
{"pattern": "Service", "pubkey": "", "privkey": ""},
{"pattern": "Servicen", "pubkey": "", "privkey": ""},
{"pattern": "Serviceno", "pubkey": "", "privkey": ""},
{"pattern": "Servicenod", "pubkey": "", "privkey": ""},
{"pattern": "Servicenode", "pubkey": "", "privkey": ""},
{"pattern": "Servicenodes", "pubkey": "", "privkey": ""},
{"pattern": "ServiceN", "pubkey": "", "privkey": ""},
{"pattern": "ServiceNo", "pubkey": "", "privkey": ""},
{"pattern": "ServiceNod", "pubkey": "", "privkey": ""},
{"pattern": "ServiceNode", "pubkey": "", "privkey": ""},
{"pattern": "ServiceNodes", "pubkey": "", "privkey": ""}
]
}
|
|
|
|
New preview version out: http://www.spreadcoin.info/downloads/preview_wallet_0.zipFeatures: JSON file is used to automatically load/save the state of everything vanitygen related (worklist, state of checkboxes, sliders, preferences etc...) Now you can close the wallet and open it later and it will continue the vanityjobs... you don't even need to restart the vanitygen when it was running the moment you exited. it will also keep track of any not yet imported private and public keys. Please test and have fun. that's the structure of the vanitygen.json file: (you don't need to create this file, it will be automatically created when missing) {
"state": {
"running": "true",
"threads": "1",
"matchCase": "true",
"showPrivKeys": "true",
"autoImport": "true"
},
"workList": [
{"pattern": "ShutUp", "pubkey": "", "privkey": ""},
{"pattern": "SexyM", "pubkey": "", "privkey": ""},
{"pattern": "Service", "pubkey": "", "privkey": ""},
{"pattern": "Satoshi", "pubkey": "", "privkey": ""}
]
}Although you can change the json file by hand, it is not recommended. You should only let the programm change this file. |
|
|
|
12m video views for a vanity gen demo. That would be cool. lol  Found my service address  'Service.....' takes around 12 hrs and the estimated find time was spot on. @Boss Address has the wrong spelling in the pop-up Congratulations and thanks. Is there a more decentralized word than "Boss"? If not, can we invent one? EDIT: fixed the typo in the new version, see below. |
|
|
|
fixed version: http://www.spreadcoin.info/downloads/preview_wallet_0.zip(replaced old link) Fixed: 1) Import Button only activated when wallet actually unlocked. 2) Improved the importing mechanism and did a stresstest importing 1000 generated vanitygen addresses (starting with SPR) all at once, and it worked.  Takes about 1 sec to import.  Filesize of wallet.dat after import went from 80 Kbyte to 544 Kbyte. |
|
|
|
BLUE ALERT BLUE ALERTTHis is very VERY impootant, plez red cheerfully, tanx xXx  No, seriously Don't use the vanity address generator if your wallet is locked.There's a little bug that allows you to import to "receive coins", but if you undertake this while your wallet is locked, your wallet may not save the privkey rendering that address unaccessible. Best to just wait for a fix before playing anymore, georgem is already on it. I concur, thanks for pointing this out. The problem is, that the "Import into wallet" button will show as active even when your wallet is locked, and this will then give you the impression that an address has successfully been imported, when in reality it has only pushed the address to your addressbook list, and will treat it as if you have no access to the privatekey, so you might actually LOSE ANY MONEY YOU SEND TO THIS ADDRESS. I have already found a fix, and am testing it right now. I will upload a new version within a few minutes. Thanks to defunctec for testing! Please continue the testing until you break it! Fixed already! It must be nearly 2am where you are. Thanks! when people's SPR are at stake I need to solve the problem immediately... |
|
|
|
BLUE ALERT BLUE ALERTTHis is very VERY impootant, plez red cheerfully, tanx xXx No, seriously Don't use the vanity address generator if your wallet is locked.There's a little bug that allows you to import to "receive coins", but if you undertake this while your wallet is locked, your wallet may not save the privkey rendering that address unaccessible. Best to just wait for a fix before playing anymore, georgem is already on it. I concur, thanks for pointing this out. The problem is, that the "Import into wallet" button will show as active even when your wallet is locked, and this will then give you the impression that an address has successfully been imported, when in reality it has only pushed the address to your addressbook list, and will treat it as if you have no access to the privatekey, so you might actually LOSE ANY MONEY YOU SEND TO THIS ADDRESS. I have already found a fix, and am testing it right now. I will upload a new version within a few minutes. Thanks to defunctec for testing! Please continue the testing until you break it! |
|
|
|
I think we need an update this week.
Will draft a summary for Tuesday.
Yes, please do so. I will also finally release the wallet for win, mac and linux and on github. I hope to finish it by tomorrow. Maybe soon enough to make it into your draft. |
|
|
|
I can fit 10 daemons comfortably on a 2GB server with a low end CPU. I'm talking about *coind, not *coin-qt. Maybe you'd need 3 64GB servers... point is it aint much.
And bitcoin bodes can be run on IPv6 addresses, either directly or via a tunnel. IPv6 addresses are practically free.
Yes coind, that's why I repeatedly said "daemons". You can maybe put 10 "idle" daemons on a 4 GB server, but the moment they actually need to do some work (verifying, etc) they will totally crash the system. Hey, everybody is invited to back up his claims, I will post a few screenshots later of the CPU and RAM load. (starting up, synching process and idle) During validation / verification process when a new block has to be checked I have repeatedly seen CPU spike to 100%, because this is a process that gets high priority by the system, because it needs to be done fast so as to be ready for the next block. And bitcoin nodes can be run on IPv6 addresses, either directly or via a tunnel. IPv6 addresses are practically free.
We can insist the server use a IPv4 address. I agree that this is a problem that has to be solved: how to discourage the running of multiple nodes on 1 server. |
|
|
|
|
Having the ability to run a full bitcoin node side by side with a servicenode will open the door for many more future services,
helping the bitcoin network is merely the first obvious one.
|
|
|
|
Looks like we've passed the Crouton test. @devs when can we start scheduling the allocation of mining rewards to node owners? Obviously we need some nodes up on mainnet, but we might as well signal the reallocation to the miners while there are so few to complian  I guess the next step after the final version of the QT is released should be the roadmap for servicenode testing... Agreed. I will have the release version ready probably by monday. |
|
|
|
Two servers with 64GB RAM each and a few TB of storage can easily run a thousand full BTC nodes. This isn't a big expense, ...
If SPR node ops can run a thousand BTC nodes for a few $ a month each, so could BTC zealots,...
I tried installing as many daemons as possible on a 24 GB RAM server a few months ago. I was only able to start about 15-20 of them before running out of RAM. (And most of those daemons were for small altcoins that didn't have the high verification needs of BTC (lots of CPU, often up to 100% during synching)) 1000 daemons on 2 servers is not possible, you need to spread this over a few dozen servers, plus it will probably cost you a few thousand dollars a month. Also, with SPR we will have the requirement that every node needs to run on a unique IP. So having enough servers to be able to run 1000 daemons is one thing, but having unique IPs for every single daemon will cost you a fortune. Every month. |
|
|
|
What does Spreadcoin get out of supporting the Bitcoin network?
It's like when the flea on the back of the dog wants the dog to be healthy. |
|
|
|
|
Show Posts
