Topic: [ANN] SpreadCoin | Decentralize Everything (decentralized blockexplorer coming) - page 303. (Read 790393 times)

^Why has it taken you so long to get into crypto dev mode?

You're obviously very good at it.

I see a user choosing what wallet / fork he wants to use as an important voting process. It gives power to the community.

A user should always have the last word whether he wants to update to a new wallet (be it one that introduces a blockchain fork, or one that simply adds new features outside of the blockchain),
eitherway the user can just as well decide that a future update is wrong (inappropriate or even dangerous) and decide to not support it by staying on the earlier fork.

So I am not sure what value auto-update systems will bring, other than more centralization. (it even creates an attack-vector, making hackers try to corrupt wallets by attacking the updating mechanism)
Deciding what wallet version to run should always be a conscious decision and never something that is in auto-mode.

NOW, if we can instead imagine sort of a sophisticated auto-notification system then I am all for it.

Kinda like the alert-system that is already built into every coin that exists, but maybe we can make it more appealing and elaborated?
Not just a small text at the bottom of the wallet, but something visualy more exciting which also explains why an update would be a good thing?

Kinda like pretty much all software I use keeps reminding me now-and-then that there are important or even critical updates available.

At the moment the alert message can only be issued by a few selected people, so this is clearly highly centralized.
Maybe we can think about a new way of alert messaging where servicenodes themselves can issue alerts/updatenotifications when they are in the clear majority...

Q.

If wallets can be protected, would docker or some other type of auto-update system be able to keep Spread wallets updated without users having to do anything particularly complicated?

That was a big one

Does anyone run a wallet on a Raspberry Pi?

Thank you, this worked.

Put this in your conf file:


Then wait, it takes about one minute after you restart your wallet to connect with those nodes.

My wallet ceased to be synchronized, though earlier everything was normal. 0 active connection(s) to Spreadcoin network. Help me.

I do have a proposal that I'd like you brainstormers to explore and research a little bit in your spare time:

Namecoin wanted to create a decentralized domain name system, but they failed because

1) their pricing model doesn't make sense.
2) users can't just browse .bit domains, they need additional tools.

So they ended up with a horribly squated namespace where some people own thousands of domains while paying only pennies (to the miners).
And those domains aren't even valuable, because only a tiny minority can even access them.


So I think this would be another nice sideproject where spreadcoin could show how a persistent problem can be solved efficiently.

So let's figure out a way how to use servicenodes to fix the pricing problem that namecoin has. (that makes bit domains very cheap to register, which encourages squatting)

Maybe some sort of voting system where servicenodes (and miners) are allowed to give a vote about how much SPR a domain is supposed to cost?

Purchasing Power Voting?

If we figure out a solution, what TLDs should spreadcoin register?

*.coin? *.spread? "Any" domain space?

We can then make it easy for people to browser those domains by embedding a DNS resolver into our wallet, that will give OSystem wide access to our domain spaces.
(Namecoin has those tools too, but outside of their wallet as third party tools, e.g. http://www.freespeechme.org/ or http://www.meowbit.com/ )

This is all just an idea ATM, but part of the decentralize everything mantra.
 

I agree that it's a chicken and egg problem, but not only in the way you mentioned.
There is yet another chicken and egg problem embedded within the servicenodes concept itself:

We can't have servicenodes without services, and without services it doesn't make sense to run a servicenode. Scoring and Voting won't function.
That's what takes so much time, because I can't just bring "empty" servicenodes into existence, they need to come complete with atleast 1 service.
(the main candidate for this first service is running supervised bitcoin nodes.)

Additionally servicenodes need to be ready to allow expandability with new services (this has to be ready from the gitgo)
(And I mean just expandability and not necessarily modularity, because the main goal (for network strength) will always be to encourage every servicenode to run ALL services available
 ----> negative score for every service you can't run.)

So to my fellow devs and project members I say: Stay tuned.
To the impatient day traders I say: Chill out.

I asked for full spreadcoin nodes, I added you because you happen to run a full spreadcoin node.
Everything else is conjecture.

Exactly and while you chaps work hard on delivering a platform we can build on, the rest of us can work on the next steps 

Sometimes its the chicken and egg problem, because if some people do not see up front results, they dismiss it and move on, while results tend to take time to manifest themselves.

right now we need to get the basic systems up and running, we cannot show something which is not finished.

so basically the overall gameplan is more or less, get servicenodes up and running, get moved over to core sourcecode.

servicesnodes are going to be the infrastructure needed for anything we want to do,

and core is going to help making things more modular and secure at the same time.

combined, we would end up with at good foundation to grow on.

i get back home tuesday, and that means more time i can dedicate to moving spreadcoin over to core, while georgem works on getting servicenode up and running..


when both these tasks have been completed, we will merge those 2, and then can we start having some decend stuff build on top and move faster ahead...

I would be keen to know how much of the block rewards are going to be allocated, if any, to nodes.

I'm sure this is up for discussion and will need to be tackled at some point.

The current financial plan is self-sustaining once income is generated by the services. So we could start with some incentives, keep them going forever or direct them elsewhere at some point: more marketing, internet infrastructure for Africa, political campaigns, etc.

Great post.

EDIT:  I look forward to announcing "Service TBA" as and when we are in the position to do so 

Compared to some start-ups I've seen, this one is moving at a pretty decent rate.

The typical start-up process usually involves months or years of chasing funds before they can get started with writing a single piece of code.

Anyway, this is the skeleton of the financial plan for servicenodes income:

https://docs.google.com/spreadsheets/d/1ov0YKQwPzqgkLarfvXWvugzQ3dne3gtkW7-5MV2kHk4/edit#gid=0

I have taken out some details, for now.

What we can see is that as services are added the overall network income grows, as does the amount that can go to core development.

As discussed previously, businesses can form around these services. Which means investors can invest in those businesses, without having to buy a single SPR if they don't want to.

It also means we can create packaged up business units and sell them on a franchise model. This helps ordinary Joe public that just wants to get going and doesn't want to think about creating documentation or risking funds on a start-up with an unproven product - they just want a turn-key business.

Franchising is one of the biggest business drivers in the USA.

All this is enabled by the nature of ServiceNodes and building Blockchain Based Businesses (B3).

So, I'd say we actually do have a plan, a team that can deliver it and a desire to profit from it.

The question isn't does SPR have a plan. The question is do you have a better plan or do you follow a project with a better plan?

Maybe we're missing something here.

Where does it mention in the ANN about service nodes and decentralized app/service provision?

It should include some use cases as examples imo.

EDIT:  The work I'm doing around communication and engagement can be published when its ready.  As can the news from my other workstreams as and when we get some.

I think we're falling into the trap of being so busy that we have a clear view in our minds but not doing enough to tell people about it.  If ok with people I'll start looking at where the gaps are this weekend.

Hey OC,

As we discussed before I personally support you in the fact the wording around pools needs to be changed. The thing is that Georgem and team are going through an intense phase of preparation work in order to fully understand and prepare the code that Mr Spread left behind for the future and me discussing this with georgem has been lost in the list of things to do.

There is a huge amount going on with SPR at the moment and a lot of teamwork and collaboration going on behind the scenes. In some ways it might have been better to wait a few weeks before starting a new ANN thread but then again brilliant discussions about the future of SPR were happening on a thread that we had no control over.

I also agree that the plan for SPR is vague right now however once the devs are ready, a plan and updated first post will happen combined with a proper community newsletter.

To say that we dont want help and assistance is a little disingenuous although I also understand your concern has seemingly been dismissed. I can assure you that I've not forgotten to push your point forwards.

Finally, from my perspective in a business development role I am unable to contribute to any announcements or roadmaps because all of my discussions are commercially sensitive until agreed by all parties.

Dan

"they" do not want help/assistance. There are 1-2 good and competent members in the team, but the rest is pretty "stall" and illusionary... For example they added my SPR pool as node, but still reject changing the topic from "No pools" to "with pools" or at least remove that no pools statement etc.. 

If you want to get a coin / project going - its 90% about team-work if its open source...

well, considering there is clear direction (semblance of an organized management structure with georgem spearheading the campaign and other members providing development assistance) and plans for servicenode implementation, no I do not think this is a valid criticism