Chaps
I've been thinking about this for a few days and I'm in the 'yes, do it' mode at the moment.
I'm thinking of launching a DRK clone, but using spread solo mining.
I'm thinking of taking on board the branding issues people feel is a problem with DRK going mainstream, adding the SPR solo mining, then just keeping tabs on developments with DRK and other clones and making sure the best bits gets into the new coin.
I have a name picked out and an additional strategy to rival DRK, while still using DRK and SPR code. I am also in discussions with a couple of good devs who could provide the necessary support.
Any thoughts?
Before I stumbled onto SPR I was planning something similar, but I was going to learn how to do it myself. I was getting there slowly, lets just say I've mined quite a few genesis blocks on my LAN...  You need to consider how much a talented and motivated developer is worth - SPR already has one, and you'd be better off funding SPR development because I can tell you right now that any plan to get a successful coin (anything beyond a ten week lifespan pump and dump shitcoin) launched by paying some dude on the intertubes to hand you a generic LTC clone is doomed. Because that's all your going to get for your 3BTC and even I can do it. If you want someone that has the skillset to understand and improve on Darkcoin code you're looking at significant and ongoing outlay. Pay peanuts, you get monkeys. About the branding thing, my own belief is that it doesn't matter, DRK's market share would be exactly the same at best and probably much lower if was called GenericMarketReaearchApprovedFluffCoin. Bitcoin's real world marketshare is practically zero - it has exactly nothing to do with the name. That said, the more I think about it the more I like the name Spread. It's not shiny and glamourous, but it's apt, it encompasses the basic principle of a distributed currency. |
|
|
|
It seems nobody is willing to sell @25K sato at cex  that is a sign that the coins are controlled by a small group. that spells trouble for new investors and community members. think I'm staying away. Why is it trouble? Tis better we get the CHAINZ block explorer, to analyse the distribution. The present one's really a headache. I asked fairglu who runs chainz and his price is $150 in BTC per year. In the meantime: http:// www.multifaucet.tk/index.php?blockexplorer=SPR&top_addresses=100 edit: this looks promising, I might have a go at building it later - https://github.com/iquidus/explorer example: http://heavychain.info/richlist |
|
|
|
Urrghh, I feel like I have to lower my IQ by 90 points to even 'think' about branding, but I read that and he's more or less right IMO. Anyone who thinks changing the name is going to have any effect whatsoever on mass adoption is delusional. If anything we'd have more luck going the other way and calling it FuckTheThievingReptilesOfWallStreetCoin. Nobody ever achieved anything worthwhile by pandering to idiots and cowards. |
|
|
|
I suspect people are waiting to make sure that Mr. Spread comes through with the masternode promise.
After new year I will have hell of a lot of free time, so I hope in the second half of January we will have some code for public testing, maybe sooner.
I am hopeful.  Solo mining by miners who actually care about and value their currency + Masternodes is a really great economic model. PS Thanks Mr Spread for the Big Backup Button! - Hopefully people will use it and save themselves future misery. If you get around to a 1-click-print-privkey(s) solution at some point that would also be fantastic. |
|
|
|
Some numbers to think about:  |
|
|
|
...snip....
If MN,darksend and especially GUI muliti-sig are integrated into Spread wallet,SPR is undoubtly to be on the list of TOP 10 maket cap.
btw: so many proposals in this thread,a roadmap should be sorted out now.
Really? You know darksend and instant tx relies on a diverse and distributed community securing the network and putting in the effort to keep master nodes up and updated? thelonecrouton has also argued (from memory, I'm sure he will correct me) that mining is less important than master nodes, so while solo mining is very attractive and closer to what Satoshi intended, solo mining can be viewed with indifference by some. To beat DRK, with an effective DRK clone, the best approach would be to advertise SPR as a re-run of DRK for those that missed the launch of DRK. Then climbing the mountain to beat DRK is a little less challenging. The lack of liquidity will remain the issue to moving this project forward in the short-term as Master Nodes are built around proof of service which requires coins. Then there is the SPR code. Anything of potential value to SPR and DRK can be used by DRK. Sadly, as you've posted this, I think I'm talking myself out of SPR. Maybe that's the second bottle of Saint-Joseph talking. Let's see what view sobriety brings tomorrow. 1. Masternodes are very easy to set up and almost effortless to administer. 2. Solo mining is actually useful, and should IMO be rewarded more highly than the eventual 70/30 split with DRK. 50/50 would be fine with me. 3. I'm happy to see quiet, steady technical progress without all the chart chasing. "No liquidity" = "I can't buy as cheaply as I want to." 4. Developmental synergy is a good thing and beneficial to both currencies. 5. You're too smart not to buy into this. |
|
|
|
Is there a guide somewhere that explains what "dumpprivkey" actually does? It's mentioned here in this thread again and again but I've never seen any real explanation of what this achieves, why it's important and how it helps protect you. I'd really like to see more plain-English explanations of these various functions and how to maintain best practise with wallets re hot and cold storage, paper, etc.
Help > Debug window > console: 'walletpassphrase <passphrase> 30' 'dumpprivkey <address>' *note, you may have more than one address in your wallet that has coins in it, dumpprivkey for each address or move all coins into one address first* - copy/print/keep safe the privkey, then, when disaster strikes: Help > Debug window > console: 'importprivkey <privkey>' Simple. Sorry lonecrouton but that is the sort of answer I'd expect from some arrogant young punk on a support line somewhere. Perhaps you're being sarcastic? I'm waving the "hey guys if we want to see wider adoption this thing has to be lifted up out of technobabble speak" flag and your "simple" response is just more technobabble. I'll ask again. Is there a plain-English guide to some of these commands that explains what they achieve and what the best practise is to ensure you're not going to lose your coins? What more do you want? What part exactly are you confused about? Since you are here on the internet posting in a cryptocurrency thread I didn't think 'Help > Debug window > console' followed by a few simple words to type into the text entry box would be quite such a baffling and insurmountable intellectual challenge for you. |
|
|
|
Is there a guide somewhere that explains what "dumpprivkey" actually does? It's mentioned here in this thread again and again but I've never seen any real explanation of what this achieves, why it's important and how it helps protect you. I'd really like to see more plain-English explanations of these various functions and how to maintain best practise with wallets re hot and cold storage, paper, etc.
Help > Debug window > console: 'walletpassphrase <passphrase> 30' 'dumpprivkey <address>' *note, you may have more than one address in your wallet that has coins in it, dumpprivkey for each address or move all coins into one address first* - copy/print/keep safe the privkey, then, when disaster strikes: Help > Debug window > console: 'importprivkey <privkey>' Simple. |
|
|
|
It's a good idea.Security is of great importance.
My proposal is a GUI muliti-sig Spread wallet.Nobody has developped a GUI muliti-sig wallet up to date.
Armoury does a reasonably good job of multisig and uses the standard backend (unlike Electrum which uses node.js) but there's a limit to how simple you can make it, it's a cumbersome procedure. If anyone is interested I did some multisig GUI examples for Darkcoin here: https://darkcointalk.org/threads/quick-and-very-dirty-multisig-ui-in-python-qt-new-unimproved-perver.2197/ - I am not a coder and don't speak c++ so can't work it into the standard bitcoin-qt wallet that SPR uses, but it would be easy enough for someone who knew what they were doing. If time is an issue though I'd rather Mr Spread concentrate on Masternodes and IX. |
|
|
|
1. Could the wallet have a startup password, or PIN from drop-down boxes, or some other method of protection at startup? It has always bothered me that anyone can come along and view my balance and transaction history. (Although I usually store the wallet.dat encrypted when not in use.) It could be set on/off via checkbox or .conf file.
You mean without any actual encryption, just password for gui? This may create a false sense of security while there will be none, anyone will be able to copy your wallet.dat and see your transactions, unless I misunderstood you. You can use OS level user password for that, I think it is more appropriate and will also protect your other private data such as web browsing history, etc. I meant something like automatic encryption of the wallet.dat file, requiring a password to unlock it before it gets loaded by the QT client or deamon. As I say I do this manually myself already, so it's no big deal for me, but having it built into the GUI/daemon might be more convenient. I appreciate you have limited time though, so just a suggestion. |
|
|
|
Vapourthink. If it ever gets beyond an academic whitepaper, and it isn't even that yet, it will be because someone else has adopted it. Bitcoin never will. |
|
|
|
|
Mr Spread, may I propose two feature requests for your consideration:
1. Could the wallet have a startup password, or PIN from drop-down boxes or an on-screen keyboard, or some other method of protection at startup? It has always bothered me that anyone can come along and view my balance and transaction history. (Although I usually store the wallet.dat encrypted when not in use.) It could be set on/off via checkbox or .conf file.
2. Add either a periodic automatic wallet.dat backup to a different directory, or stick a big BACKUP WALLET button on the overview form. Also, on initial startup (or creation of a new address) a popup asking the user if they would like to print the privkey(s) for safekeeping - dumpprivkey is the first thing I do before funding an address and it has saved me several times.
edit: a virtual keyboard option to enter passphrase before sending would also be great.
|
|
|
|
I absolutely love Darkcoin and all the people that make up this community, but reading through all that's just happened to xxxgoodgirls and what stonehedge went through with the hack he suffered recently one would have to come to the conclusion that managing your locally stored Darkcoin is far from certain and assured. It's alarming to me that substantial amounts of value can be lost so easily and with such accompanying confusion that entraps even very experienced people.
Until the retention and securing of coins in wallets can be lifted up and out of this level of technical confusion and need for extreme (almost forensic) troubleshooting, Darkcoin is NOT going to be used by regular people. To read through pages and pages of someone battling to understand where their thousands of $ have gone and finally admitting defeat is terrible (so sorry for your loss xxx; l sure hope something gets resolved and you can retrieve your DRK somehow).
This really is an aspect of crypto that will prevent many people from getting involved (read: virtually everyone who is outside of these levels of technical ability which is 99.9%), We really need to spend a whole lot more time and effort on firming up wallet apps and infrastructure if Darkcoin is to be taken seriously as the potential to inexplicably lose all your DRK is very real.
I think you're being a bit pessimistic, but what I would like to see is automatic periodic backup to a second location of the wallet.dat, and a big popup on initial startup of a new wallet (or creation of a new address) encouraging the user to click a button to print out their privkey(s) - with "KEEP THESE PRIVATE AND SAFE!" at the top of the page and instructions on how to import them. |
|
|
|
I generated the privkey and get address 0, I have them noted as well.
If you have the privkey for the address you sent to, just 'importprivkey <privkey>' at the console and you'll get that address and balance back. Which is why you should always dumpprivkey, print it out and keep it safe for any address before you send funds to it. |
|
|
|
http://www.[Suspicious link removed]/index.php?blockexplorer=SPR&top_addresses=100 top 100 rich list ,doesn't change much in the past weeks. http://www. multifaucet.tk/index.php?blockexplorer=SPR&top_addresses=100 |
|
|
|
come on chaps: 1,376,181 distribution and no liquidity?
There's perfect liquidity, in all markets, at all times. You just have to pay enough. |
|
|
|
Good article, short and to the point. |
|
|
|
So I'm thinking of putting in some effort.
Before that:
WTB 100k SPR
I'd pay 22.5BTC to have coins on my team. He kept DRK on the straight and narrow for a fair time. Either that or he just posted on the thread a lot. Its hard to tell. EDIT: There aren't enough on Bittrex for that buy. A buywall for nearly 10% of the entire currency would be nice to gawp at though. Alas I'm tapped out for the month, all those Xmas presents for myself weren't cheap. |
|
|
|
 Solomining Spreadheads aren't going to sell their beloved SPR on the cheap to a pack of sharks like you lot. Put your buywalls on bittrex and allcrypt like the rest, eh?
|
|
|
|
I have suggested it before:
Why not move the Masternode network completely and solely into the IPv6 space.
Every node could have an arbitrary amount of addresses, bound to an arbitrary amount of wallets.
The node addresses could even be changed all the time by some maintenance protocol.
How would non-IPv6 clients be able to connect to a masternode? I believe most end users like myself currently do not have access to IPv6 through their ISP. Could MNs run their own DNS service - no more need for a fixed IP? Not sure exactly what problem this would solve. AFAIK there is also no requirement for a fixed IP currently. The protocol allows to send a dsee message to update the address of a masternode for a VIN. Really? So I can change the IP of my server (or have my ISP periodically assign me a new one if I'm running a MN on my domestic connection,) keep everything else the same, and it will still work? Guess I missed that memo. Do you not still have to update your local/remote .conf files with the new server IP? |
|
|
|
|
Show Posts
