Err.....well, you see...let's just maybe hold off for a bit. It would be nice if there was a bit more transparency here... An Android app is in the works, but I haven't seen the details to know if that extends to a wallet. If it becomes an issue, which I doubt, we can fund a wallet so it doesn't distract from the main focus. An app? Cool, any info on the app's functions? First app is simple. It shows basic market data and the value of your wallet. Second app will notify you on service node payments or mining rewards. Should be ready in the next few days. I'm testing at the moment. That's brilliant! So the first app is nearly ready and the second has to be built yet? |
|
|
|
Err.....well, you see...let's just maybe hold off for a bit. It would be nice if there was a bit more transparency here... An Android app is in the works, but I haven't seen the details to know if that extends to a wallet. If it becomes an issue, which I doubt, we can fund a wallet so it doesn't distract from the main focus. An app? Cool, any info on the app's functions? |
|
|
|
|
Anything to share georgem? A couple line update would be lovely... I hate to press you but it seems like nothing is happening?
Thanks!
|
|
|
|
Err.....well, you see...let's just maybe hold off for a bit. You mean, it may get done for free? |
|
|
|
Awesome! All very familiar names  I'm sure there are many more. I really hope georgem is successful in releasing SN's to testnet as it will be a pleasure to test SN's with you guy's! I tested alot with Darkcoin, spoke with Evan a few times and sent him a couple of debug.log's. Also spent wayyyy to much time testing Spreadcoins 'masternodes' at the time  I literally cannot wait for georgem to announce testnet  |
|
|
|
I have a little game to pass the time...  If you've followed Spreadcoin for longer than 4 months and are still invested, type a reply with +101. It'll be cool to see how many individuals follow SPR. |
|
|
|
Uncommon problem - I have mined quite a lot of blocks and want to move to another address/exchange. Now when I try to send about 900 (quantity?! I am not sure how these are called - in this particular case they are the blocks) there is a fee and the transaction goes through:  The problem is when I try to send more (quantity) I hit the maximum for a transaction and wallet would not process the transaction. The following appears after I enter my wallet encryption key and hit enter:  And then:  What is the limit of a transaction (max quantity or bytes or something)? I could go ahead and select them (quantity/blocks) manually but that would be a physical and mental challenge: ARROWDOWN, SPACE, ARROWDOWN, SPACE, ARROWDOWN, SPACE, ARROWDOWN, SPACE, ARROWDOWN, SPACE, and so on... thousands of times! That "problem" is very peculiar and I wouldn't think it would a be a very common one. Still - does anybody have any ideas how to proceed, so I make my life easier? Too many dust transactions: It happens often. You should use "coin control" in order to combine some of the largest unspent outputs you have in your wallet with a few of the smaller ones, creating bigger outputs: repeat this as many times as needed until you reduce the too large number of tiny outputs you've got in your wallet. ... Options > Display coin control featuresand then Send Coins > InputsI don't see how this will help me - and if not - why do you bother just repeating what I already talked about? As you can see from the screenies I already use coin control. And I understand what is going on. My questions are - what are the limits and is there any way to use console commands for coin control? Once in coin control > inputs > list mode, check 1/4 of the boxes and send as one transaction... Do this for the rest of your inputs and you should be good. I have no idea if this can be done with commands. |
|
|
|
Nodes at home are facing some serious bandwidth issues:  How much does this kind of bandwidth usage cost? Does the 'more people use bitcoin' argument explain this surge in bandwidth? |
|
|
|
I expect that I need another 50 hours or so to finish everything and put all the loose ends together before we can start testing it.
This could mean best case, that I will be ready in 1 week, or worst case by the end of january.
Is end of January still looking feasible? Pretty much. I was able to do about 50% of what's still needed. If might not be able to finish the other half in the next week (collisions with dayjob), so it might slide a few days into first week of february. I'll probably create an explanatory video about current state of overlay network and how the blockexplorer behaves, so you better know what the problems are I'm working on. I owe you that much. Any news? Any update? |
|
|
|
huh. well thats weird. my spreadcoin wallet at bittrex is disabled.
anyone know whats up with that? not comfortable with depositing until fixed.
wondering if its due to a low balance? i have dust there (.05 spread) just as a kind of "placeholder"
Get a support ticket from them and report back? I have the same problem, maybe the wallet is being updated? |
|
|
|
Is it me or does it feel like we're in the eye of a storm?
no storm ... i feel like we are at the base of a city construction site - that is about to begin ... solid construction and progress ahead is all i see ... skyward people - skyward ...  ... #crysx I meant in the market not in general, no one is selling much and ServiceNodes are due  |
|
|
|
|
Is it me or does it feel like we're in the eye of a storm?
|
|
|
|
|
Cool, got a reply from mr Lopp, hope he keeps an eye on Spreadcoin
|
|
|
|
Sorry for not being very active here right now. big update coming soon. As in a verbal update about current progress or a big update on the release of SN's in testnet? 'please the latter, please be the latter!' |
|
|
|
I'm talking about somebody runnning 500 bitcoin daemons as full nodes from one copy of the blockchain with 500 service nodes.
Those would have to be special custom versions of bitcoin daemons, to be able to link with the same blockchain. (only one would be writing, and the others would be in readmode, answering to external nodes. They would be mere mirroring/echoing nodes. They might alternate this assignment with one another.) To the rest of the bitcoin network they would appear normal, except that they would have this unnatural synchronicity ( no time or height differential whatsoever) Shouldn't be that hard to create even for an average dev. He would have to remove any locking restrictions from the code, and remove any update/writing capabilities. He would keep everything in there that is for listening and answering requests, like getheaders, getdata, getblocks, etc..) If you have access to a server with 2 IPs and network storage maybe you can run a test and see what happens. (It won't work) Maybe someone could create one of these mirroring/echoing-nodes until it indeed works? That would be quite interesting to see. Thanks for the info. Challenge accepted Any results to report ? Believe it or not, I haven't managed to sync the bitcoin blockchain since then. OK, my day job is taking up 90% of my time at the moment but 60gb is taking a long time to dl and index! Fair enough, im eager to find what happens. |
|
|
|
I'm talking about somebody runnning 500 bitcoin daemons as full nodes from one copy of the blockchain with 500 service nodes.
Those would have to be special custom versions of bitcoin daemons, to be able to link with the same blockchain. (only one would be writing, and the others would be in readmode, answering to external nodes. They would be mere mirroring/echoing nodes. They might alternate this assignment with one another.) To the rest of the bitcoin network they would appear normal, except that they would have this unnatural synchronicity ( no time or height differential whatsoever) Shouldn't be that hard to create even for an average dev. He would have to remove any locking restrictions from the code, and remove any update/writing capabilities. He would keep everything in there that is for listening and answering requests, like getheaders, getdata, getblocks, etc..) If you have access to a server with 2 IPs and network storage maybe you can run a test and see what happens. (It won't work) Maybe someone could create one of these mirroring/echoing-nodes until it indeed works? That would be quite interesting to see. Thanks for the info. Challenge accepted Any results to report ? |
|
|
|
I'm looking at you, kid!  lol, no means no right? |
|
|
|
I expect that I need another 50 hours or so to finish everything and put all the loose ends together before we can start testing it.
This could mean best case, that I will be ready in 1 week, or worst case by the end of january.
Is end of January still looking feasible? Pretty much. I was able to do about 50% of what's still needed. If might not be able to finish the other half in the next week (collisions with dayjob), so it might slide a few days into first week of february. I'll probably create an explanatory video about current state of overlay network and how the blockexplorer behaves, so you better know what the problems are I'm working on. I owe you that much. Let me get this right. By the 7th (latest) i will be able to test a service node on testnet? If so will they have decentralised block ex? |
|
|
|
This guy runs a mining and hosting for a fee operation, so he knows about costs (I suppose the Chinese don't really pay electricity). Interesting that the risks to Bitcoin that we thought would be really big risks are being brought up by those closest to mining: The Bitcoin halving this year will be painful, unless there is a price increase, but the halving in 4 years time is a 'survival' event. http://pastebin.com/B8YQr5TQIf the price didn't increase and block half'd, wouldn't miners switch of their rigs? lowering price per transaction? Yes they would switch off their rigs, except those miners in China that are based next to small hydro plants that generate electricity that no one wants, so they give it away free to Bitcoin miners for a share of the rewards. KnC has seen this risk and is also building a new facility and its own hydro plant (those guys are seriously smart). For everyone else, when they switch off, mining will be pushed even further into Chinese hands. How will this play out for Bitcoin security? Will it eventually lower the price per transaction? Who knows. So mining gets free kw's and the price per transaction drops off a cliff. The trade off will be more centralisation of mining. But full nodes are the ultimate tool against malicious miners imo, spr could offer a solution to a problem that 95% of coins have. |
|
|
|
|
Show Posts
