I wonder if it is worth cpu mining on a full node? CPU load is < 1% on mine so I might give it a go. Maybe a few extra SPR every week or two... Hopefully it won't impact on its node functionality.... EDIT: 16,670 hashes per second says its not worth it
|
|
|
and 330k spr Just trolling a little How the pro's troll: Been syncing for a few hours, gone from 7 to 17 connections. { "balance" : 820215.08398676, } If our top secret meeting goes well can I have the 5.08398676?
|
|
|
and 330k spr Just trolling a little
|
|
|
34 connections { "version" : 91504, "protocolversion" : 70019, "walletversion" : 60000, "balance" : 330493.00000000, "blocks" : 385026, "timeoffset" : 0, "connections" : 34, "proxy" : "", "difficulty" : 14.85179595, "networkhashps" : 1159289318, "moneysupply" : 2575326.48712499, "testnet" : false, "keypoololdest" : 1430933717, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" }
|
|
|
Good job on the new website!
I'm interested in running a node, but I have Windows 2003 Server: how does it work on this platform?
If you didn't mind having a the QT open I assume its as easy as just creating the conf file and running the QT! Not sure about running the daemon under windows, have never tried with any coin before.
|
|
|
Bounty won
|
|
|
My gut feeling (as a non developer) is that Bitcoin core is the only way to go for now.
Big thanks to Xojex for his help with a full node user guide. It will shortly be published (with screenshots) on the SPR forum and also in the new Github when it arrives.
|
|
|
I'd rather we repeat what Darkcoin did with Kristov Atlas. (when they raised 1000 DRK for his review), instead of "employing" someone.
Interested people should approach us on their own (because they like our project, not because we are going to pay them), and if they are going to make extensive technical reviews, we should start a donation based crowd funding as happened with Kristov Atlas. (plus what will come out of the devfund).
Just one small observation if I may. I'm sure many people spotted it from outside the community but nobody within the DRK community voiced concerns about this at the time. I think it is important that if we raise donations for somebody to do technical/code/security reviews then MUST make sure that we don't donate to them in Spreadcoins. BTC or FIAT should be the only options. I have total trust in Kristov's integrity and acknowledge that he devoted a lot of time for not very much recompense to his Darkcoin review but the fact he was receiving donations in DRK left him open to challenges on his impartiality. Credit where credit is due, he picked enough holes in Darkcoin at the time that this was never seen as an issue
|
|
|
snip
Just a thought - if we are going to be running bitcoin nodes and we did get an affiliates program going, perhaps we can allocate some of this dev fund from affiliates to retain technical input from a bitcoin core dev, say $10k/year?
Sounds like a great idea to me. It could be used to fund/resource testnet. I know it is very early days yet but any idea when we will see the first glimpse of a high level roadmap? Are we talking days, weeks or months?
|
|
|
I think I just done gone and got a full node running. Just waiting for it to sync.
52.17.253.8 Its fully synced now. Could you try and phone home please George? Cheers Everything is OK! Thanks. I WIN AT LIFE! Thanks mate. I'll keep it running for a minimum of 6 months. That's the spirit! 20 connections and rising so all appears to be well.
|
|
|
I think I just done gone and got a full node running. Just waiting for it to sync.
52.17.253.8 Its fully synced now. Could you try and phone home please George? Cheers Everything is OK! Thanks. I WIN AT LIFE! Thanks mate. I'll keep it running for a minimum of 6 months.
|
|
|
I think I just done gone and got a full node running. Just waiting for it to sync.
52.17.253.8 Its fully synced now. Could you try and phone home please George? Cheers
|
|
|
I think I just done gone and got a full node running. Just waiting for it to sync.
|
|
|
Thought I would check out terms of service before signing up, and one provider sent a ticket request back saying - no bitcoin allowed on their servers. Waiting to see if I get a reply back on the reason why not. So I guess this will be a recurring issue. edit a response: They cause trouble! So I guess its a Bitcoin node technical issue. Can't imagine what, atm. I've heard of memory leak problems with bitcoind in the past but I can't see a VPS provider being concerned how you utilise your memory! Right...I have a couple of hours free to try and get a full SPR node working tonight. I reckon its easy and you can call me Susan if I don't get it working without any help.
|
|
|
This coin must have Dev Jesus working on it. Announced on 20th April and by 7th May they've got a fully working marketplace!
I wonder why the other projects are taking months to develop their marketplaces when it is as easy as a few days work?
|
|
|
So marketplace will be released tomorrow Gosh, I can't wait!
|
|
|
For info, Xojex has offered to have a go at a text based guide for full node setup.
|
|
|
Just realised that I should be able to build a node myself. Fuck my early night!
|
|
|
Dan had another good idea last week.
Coordination using Slack. It also looks free for lite use.
I've never used it, but it looks pretty good.
One downside to slack is that if you have a small community it reduces activity on your BCT thread. SDC are dealing with that challenge at the moment. Its a great way to collaborate in a nice snappy chat format though. For some reason I can't insert links into PMs to vertoe. I'll try again tomorrow. Early night for me. Have a good night ladies and chaps.
|
|
|
As a fan of textual guides rather than videos, I'll offer a 2,000SPR bounty to the person who produces a nice clear step by step guide to setting up a full node (with screenshots if necessary). Vertoe's testnet guide is really easy to use...something like this http://spreadcointalk.org/index.php?topic=45.0I reckon it should be pitched at confident techies with little or no Linux experience.
|
|
|
|