Alternatively I'd be very happy to temporarily open SSH up to you and lend you the pem file  But that way I don't learn... |
|
|
|
Vertoe's guide has got me to compiling stage no problem but no mention of firewall rules...
Also, this is a guide for masternode setup. What needs to be in the conf file for a full node?
D
This: rpcuser=SOMETHING
rpcpassword=VERYLONGCOMPLICATEDPASSWORD
maxconnections=1000
timeout=20000
port=41678 Thanks George. Should be ready to run soon. I'm actually having a few problems. Well I might be. I don't know. When I tried to start spreadcoind it told me that the .conf file was missing from testnet3 directory which isn't a path I specified. I wonder if vertoe's instructions were a little bit too oriented to testnet masternodes? Spreadcoind is running but I'm not seeing blockchain downloading. I also saw this message when I started it: [1] 1203 I've probably ballsed it up. EDIT: I'm an idiot. I did this: git checkout mn-test Yeah, I am sorry, coins101 gave you wrong advice here. This has nothing to do with the masternodes testing we did a few months ago. ::Shakes fist angrily at Coins101!:: I have an instance running and waiting to be a SPR node. I have limited Linux experience but I learned how to create and update DRK masternodes no problem so this shouldn't be beyond me. I can follow instructions. Spell them out to me like I'm an Infrastructure Programme Manager who thinks he knows everything and you've got yourself another node.  |
|
|
|
Vertoe's guide has got me to compiling stage no problem but no mention of firewall rules...
Also, this is a guide for masternode setup. What needs to be in the conf file for a full node?
D
This: rpcuser=SOMETHING
rpcpassword=VERYLONGCOMPLICATEDPASSWORD
maxconnections=1000
timeout=20000
port=41678 Thanks George. Should be ready to run soon. I'm actually having a few problems. Well I might be. I don't know. When I tried to start spreadcoind it told me that the .conf file was missing from testnet3 directory which isn't a path I specified. I wonder if vertoe's instructions were a little bit too oriented to testnet masternodes? Spreadcoind is running but I'm not seeing blockchain downloading. I also saw this message when I started it: [1] 1203 I've probably ballsed it up. EDIT: I'm an idiot. I did this: git checkout mn-test |
|
|
|
Vertoe's guide has got me to compiling stage no problem but no mention of firewall rules...
Also, this is a guide for masternode setup. What needs to be in the conf file for a full node?
D
This: rpcuser=SOMETHING
rpcpassword=VERYLONGCOMPLICATEDPASSWORD
maxconnections=1000
timeout=20000
port=41678 Thanks George. Should be ready to run soon. |
|
|
|
|
Vertoe's guide has got me to compiling stage no problem but no mention of firewall rules...
Also, this is a guide for masternode setup. What needs to be in the conf file for a full node?
D
|
|
|
|
|
Is it just TCP 41678 that I need open inbound?
|
|
|
|
|
Alright. I'm going to give this a go. I have an unexpected free hour to get this going.
|
|
|
|
Maybe I'll run a full SPR node and full Bitcoin node on the same server |
|
|
|
So 4 dev or project members have already volunteered to run a static full spreadcoin node,
and their servers are already up an running.
Anyone else?
What about you...
...Gladimor?
...Stonehedge?
...e1ghtspace?
...defunctec?
...ScamAlert?
Would be great to get atleast 8 people on board.
EDIT: I will release a new wallet soon.
I'm a definite. Any ideas on approx bandwidth usage? Time is the only issue for me. Will spin one up ASAP. EDIT: Actually, any suggestions for all round specs? I'll prob stick with AWS for ease. |
|
|
|
|
Whatever happened to NoobKidontheblock?!
|
|
|
|
I have been watching this since January and have only seen progress.
+1 I've been following Banx since day 1 and their success so far has impressed me. For clarity, I own no Banx shares. There does seem to be a minor communication problem though. Shouldn't any queries/complaints/questions be channeled to a single point of contact such as zendesk? Its great having a personal touch but audit trail and timely responses (bank holidays excepted) should take priority. If shareholders need to contact individuals to resolve problems, support communications could be improved imho. I guess its none of my business but hey, maybe I'll buy in one day |
|
|
|
Does anybody know who "Susel" is?
He/She is mentioned in the About-Section of the spreadcoin-qt wallet:
"The logo is made by Susel."
There is a graphics studio in Australia called Susel... |
|
|
|
The maximum number of service nodes at the moment is ~880 based on a coin supply of ~2,540,000. This means that number 1 wallet would be able to run ~68 service nodes ( without worry about being dropped by the spread. Interesting stuff. 68 full service/bitcoin nodes. That would be a serious commitment to bandwidth bills Interesting, what is the calculation that you made to come up with 68? I was going by mental arithmetic so I'll show you my rough working from memory. I apologise for the mental back of fag packet calculations! Number 1 wallet has ~200k SPR Current coin supply is ~2,500,000 Max number of snodes (coin supply/2880)= 868 Based on the false premise that every coin will be used in a servicenode (I have no data to guess how many coins will be in snodes): Max coin supply / Max snodes = 2880SPR Meaning that if I was the owner of #1 wallet and I wanted to guarantee that all of my service nodes were in the spread I'd load each node with 2800SPR which means that I'd be able to afford to fund roughly 68 snodes in this way.
EDIT: Correcting price error
A quick check on AWS estimates that it would cost $3000pm to run the following:
68 x T2.micro
68 x 60GB magnetic volumes
13,600GB outbound traffic
1360GB inbound traffic (free anyway)
This means the #1 wallet holder would need to see about 130,000SPR per month (at current price) to break even)
goodness gracious, that's certainly cost prohibitive. I was thinking a remote server in the range of $ 5 month/node would be borderline feasible but would need the price of spr to reach beyond .000205 to be profitable. Since the primary objective is decentralization, why not tie cpu mining to spr's first reward service? It would strengthen the network, be something anyone could jump into with little cost, wouldn't be too difficult to implement, and provide preliminary insight into how the competition dynamics will play out. This does more to highlight the prohibitive cost of outgoing/upload traffic on AWS. There are VPS providers who can provide the required bandwidth for a full bitcoin node for far less it seems. |
|
|
|
so far mine has 8 nodes connected, it runs on its own server : 94.23.23.194
Cool, mine is 5.35.253.206 Anybody who is serious about running a full node please tell me your IP. You should be ready to let it run atleast for a few months, so only tell me if you are serious. I'm just thinking about which VPS provider to switch to. Have been using AWS for ages. I'm very familiar with it...for a semi-techie like me, familiarity is a big deal. Once I've chosen a provider I'll set up a full node. |
|
|
|
Thats addresses, not wallets  |
|
|
|
Just synced up, and I can only see 7 connections.
Wait a few hours... mine still keeps slowly increasing.... 57 now. spreadcoind getinfo
{
"version" : 91504,
"protocolversion" : 70019,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 380496,
"timeoffset" : 0,
"connections" : 57,
"proxy" : "",
"difficulty" : 15.88394853,
"networkhashps" : 970883038,
"moneysupply" : 2548016.32889999,
"testnet" : false,
"keypoololdest" : 1430672087,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
I have no idea how many spreadcoin wallets there are worldwide? Any guesses?  I like the numbers I am seeing. I guess 65,175 |
|
|
|
The maximum number of service nodes at the moment is ~880 based on a coin supply of ~2,540,000. This means that number 1 wallet would be able to run ~68 service nodes ( without worry about being dropped by the spread. Interesting stuff. 68 full service/bitcoin nodes. That would be a serious commitment to bandwidth bills Interesting, what is the calculation that you made to come up with 68? I was going by mental arithmetic so I'll show you my rough working from memory. I apologise for the mental back of fag packet calculations! Number 1 wallet has ~200k SPR Current coin supply is ~2,500,000 Max number of snodes (coin supply/2880)= 868 Based on the false premise that every coin will be used in a servicenode (I have no data to guess how many coins will be in snodes): Max coin supply / Max snodes = 2880SPR Meaning that if I was the owner of #1 wallet and I wanted to guarantee that all of my service nodes were in the spread I'd load each node with 2800SPR which means that I'd be able to afford to fund roughly 68 snodes in this way.
EDIT: Correcting price error
A quick check on AWS estimates that it would cost $3000pm to run the following:
68 x T2.micro
68 x 60GB magnetic volumes
13,600GB outbound traffic
1360GB inbound traffic (free anyway)
This means the #1 wallet holder would need to see about 130,000SPR per month (at current price) to break even)
The current emissions are around 250k-280k SPR / month, very roughly - using 1 min block time, 6.6 / block. Almost as "very roughly" as my calculations. AWS obviously is not the cheapest option for hosting. |
|
|
|
I am gonna release a new updated wallet soon, with new DNS seed, and updated list of seed nodes,
and new alert key.
So, who here is running a full spreadcoin node?
And how many connections do you on average get?
Mine has about 50 connections ATM.
I'm happy to run a full SPR node. How do I do it? 1) You need a server with static IP 2) Using your servers terminal (SSH) build (and install) the "headless" spreadcoin daemon as described here: https://github.com/spreadcoin/spreadcoin/blob/master/doc/build-unix.md(this will take a while) 3) Now you can start spreadcoin by typing: (append the & at the end, so that your terminal window isn't blocked...) It will take a while to make first connections and sync, but nothing compared to bitcoin, lol. Now you can keep refreshing spreadcoind to get new information about its progress with this: Once it is fully synched, and you see that it has lots of connections, tell me your IP and I will include you on my list. Mine looks like this ATM: ~# spreadcoind getinfo
{
"version" : 91504,
"protocolversion" : 70019,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 380459,
"timeoffset" : 0,
"connections" : 50,
"proxy" : "",
"difficulty" : 16.17220056,
"networkhashps" : 1023057409,
"moneysupply" : 2547793.12498166,
"testnet" : false,
"keypoololdest" : 1430672087,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
} Cheers, much appreciated. I'll build one a bit later. Time for a game of Scrabble. |
|
|
|
I am gonna release a new updated wallet soon, with new DNS seed, and updated list of seed nodes,
and new alert key.
So, who here is running a full spreadcoin node?
And how many connections do you on average get?
Mine has about 50 connections ATM.
I'm happy to run a full SPR node. How do I do it? |
|
|
|
|
Show Posts
