Topic: [ANN] SpreadCoin | True Decentralization (No Pools) | Testing New Masternodes - page 360. (Read 810079 times)

Of course, very interesting suggestions.

Don't forget that this is solo only coin. Block time should be low to allow people with less hashrate to mine.

I spent some time optimizing integrated CPU miner before GPU miners appeared but it probably requires more work though. Note that this hashrate should be lower than in X11 by design because mining algorithm itself is slower.

I was investigating quantum-resistance some time ago. It appears that all quantum resistant digital signature algorithms have insane key and signature sizes which makes them completely impractical to store in blockchain. Your proposed future-proofing won't work, to spend any of your "secured" coins you would still need to reveal your public key.

Is that because of having smaller transactions so the cpu is used more?

I have submitted another potential issue to DarkCoin dev, its significance is hard to estimate but I guess it already affected many people in a minor way, they just haven't noticed it.

I now have feeling that I'm working more on DarkCoin instead of SpreadCoin, I need to fix that. While integrating DarkCoin features is a longer term project, in a shorter term I want to make some improvements to the SpreadCoin wallet. In particular, I want to improve syncing time, right now it is too slow.

Actually come to think of it I purchased 15000 EUPH off c-cex and I only got like 14735 or something like that?  C-cex sucks balls anyways!!

OMFG!!!!!!! That is absolutely amazing news!!! I've been harassing every exchange on twitter the last two weeks to add SpreadCoin lol If Bittrex adds SpreadCoin then we will definitely see BIG MONEY flowing into that coin for sure!! Well hopefully I will be writing Congratulating Mr. Spread on his coin getting added to Bittrex in the near future Cheers everyone!!

Yay! This is good. I wonder how many coin requests bitters gets every day.

LOL that's hilarious bro that's exactly what happened with my first SpreadCoin block I found lol left my laptop overnight and woke up with 6.46 Spread in my wallet then I did some more research and realized the potential of this coin and now I'm pretty much all in lmao

Lol. I remember a long time ago I left my laptop on all day while I went to school. 11kh/s. And got home and I had 1 block!
Then I mined with my desktop for 3 hours @ 100 khash/s and didn't get 1 single block.

Is what my alt account? NoobStoryToGlory? No I just deemed myself the NoobKidOnTheBlock when I officially started trading cryptocurrencies last april lol I'm still super wet behind the ears buddy.   I mean I'm just learning how to set up miners and the only ones I can get to actually work are cgminers for scrypt lol but I'm getting a boss ass Desktop to start mining with for Christmas which is why I would love all the help I could get when it comes to setting up .bat files or even .conf files for miners and wallets and all that crap.  But ya I can't mine SpreadCoin from my laptop right now cause I only get 11kh/s which don't get you coins too often lmao

Is that your alt account or something?

Edit: I just realised that I can just make my batch file generate a .bat for mining. Much easier than what I was originally thinking.

Is bittrex aware of this coin ?
It could be a good bump for this coin to be listed in bittrex

Well I would be more than happy to test that out if you could get something like that working because I haven't been able to mine hardly any of my SpreadCoins they have all been store bought but that's okay because the NoobStoryToGlory knows a good investment when he sees one

I could probably create a batch file that asks for the pool url, username and password and extra stuff. Here you would type something like "-I 17 -auto-fan" and the thread concurrency options. I think I can make it save to a .txt file. I remember a time when I made a username and password batch file that saved it to a .txt file. Oh damn I remember that it only checked if the username and password matched. Hmm. Maybe I can figure something out.

I would definitely be down with that because the only miner I've ever been able to configure on my own is cgminer for scrypt lol and I would love a user friendly built in NOOB friendly way to mine more of these delicious coins

"7) CPU mining is ideal in the way it is conducted through the menu, but the mining speed should be faster / more optimized for certain architectures and instruction sets. This needs some work.

It would be ideal if GPU mining can also be integrated or "associated" from the mining menu... ie spreadcoin-qt calling the gpu miner program with the right parameters (that the newbie user doesn't know how to setup)."

I second that.

May I also propose a few more suggestions, beyond the fixing / upgrading of the masternode payments system?

1) Block time of 1 minute could create bloat in the long run and might need upward adjustment. It is also worth looking into a mini-blockchain integration. If InstantX is also copied from Darkcoin in the future (something that only coins with masternodes can emulate - and spreadcoin will be in that position), block time can be safely revised upwards.

2) There are two DarkSend parameters which can be tweaked for a DarkSend implementation that can differentiate spreadcoin: Default and max mixing rounds. So Spread could opt for better anonymity by default by increasing the default number of rounds and taking the max number of rounds to 10 or beyond instead of 8 max (DRK).

3) Darkcoin faced an interesting problem with the compromise between speed of mixing and sybil resistance*. With 2 participants speed was ok but sybil protection was practically non-existant (the one party mixing knew the other party mixing). With 3 participants sybil protection is much better but it can still go higher (at the expense of mixing speed). Spreadcoin can use a higher number of mixing participants if it wants to. To ensure mixing takes place and mixing parties don't wait for a very long time, a happy hour can be established where the client has a scheduler to start mixing at a predefined hour, or a certain block. In this way a lot of participants can start mixing at a predetermined point and be almost assured of mixing success. This will be less of a problem when greater adoption happens and more of a problem as fewer people are mixing.

* Resisting the attempt of fake mixing parties to take all the mixing seats and thus know the rest of the legitimate parties who are mixing.

4) DRK's Sybil resistance is relatively low right now due to not having a fee structure that acts as a preventative measure. A weakness was discovered where through the fees paid by each mixing participant => the fees betrayed the participants. Evan kind of shut down the fees to solve the issue, or used the fee structure in a way where one out of several mixings is charged. This allows a degree of Sybil abuse which needs an alternate system in place to charge participants per use (so as to penalize sybil attempts), but without revealing the participants identities.

5) A strong IP obfuscation method, integrated to the client, is a must. DRK doesn't have an IP obfuscation method in place at this point of time - although it is on the cards. Anonymity is not complete without IP obfuscation.

6) It would be good to have a system of encrypted communication so that merchant and user (or user-to-user) can exchange encrypted information that preserve anonymity (like exchanging fund addresses, providing shipping details). There are probably implementations that could be ripped from other coins or open source software, modified, integrated and adopted for use.

7) CPU mining is ideal in the way it is conducted through the menu, but the mining speed should be faster / more optimized for certain architectures and instruction sets. This needs some work.

It would be ideal if GPU mining can also be integrated or "associated" from the mining menu... ie spreadcoin-qt calling the gpu miner program with the right parameters (that the newbie user doesn't know how to setup).

8 ) Low network hashrate is a danger. Complicated solo mining (=anything that isn't click and play) creates the possibility of 51% by even moderate-size "whale farms / whale miners". This creates the need for an upgrade of (7): If mining is to be decentralized by a multitude of solo miners, low-hashrate cpu mining need to be optimized and gpu-mining must be merged or "called" from the wallet client itself in a way that is noob-friendly.

9) A real problem that DRK-clones will face, is that the DRK network has a serious value in its own masternode network. This means that breaking sockpuppet* resistance is an expensive proposition. Coins implementing DarkSend do not have the same value on their network and are thus much easier to sockpuppet by obtaining a large number of masternodes. This will require a well-thought out strategy to deal with the issue of proper value per masternode. A much better alternative -if the dev can make it work- is to attempt blind signing of transactions where the masternode does not know who transacts what. IIRC from some discussions back in April-May, Darkcoin abandoned this approach because blind signing could be DOSed in a way where the network could not penalize the attacker (as the node didn't know who was transacting). Again IIRC, Kristov Atlas in his Darkcoin review believed that sockpuppet resistance could probably be improved through blind signing.

* Sockpuppet = Fake actor controlling masternodes to map transactions

10) Quantum-resistance: The ECDSA of Bitcoin / Bitcoin clones is not quantum-computing resistant. This means that once a public key is known, a private key is weaker against a QC attack.

I believe there can be two solutions for this issue: Changing the algorithms to QC-resistant and thus creating the first QC-resistant altcoin (there is the possibility that they might introduce bloat). Alternatively a work-around QC-resistance can be created through a checkbox. When ticked, all addresses with even one spend transaction will have their funds moved, automatically, to new addresses with zero spends. This will prevent the pub key from being publicly known (and thus being reversed), if and when a QC attack occurs / if and when a QC is developed and deployed. Futureproofing in this way could create a new way of crypto-diversification asset to counter a QC-attack risk (that will leave vulnerable the other coins).

Fair enough.  Thanks for the response.

+1000 to that people SPREAD the word about SPREADCOIN to thy neighbours

I freaking love you Mr. Spread You are one solid dude bro!!! and you apparently know your shit so I insist if there is anything I can do for the SpreadCoin community just let me know and I'm on it

I politely disagree (spreadcoin) as in spread around the world makes good sense to me.  We want this to spread around the world and make us all rich.  I vote leave it alone.