In the same place where you create New Addresses. It will let you decide if you want a vanity or normal address. Vanity addresses are then listed as "processing" until they can be used.

It will not have "tabs" as you know them, but rather categories and subcategories. So expect a new mainmenu (left sidebar):



One category is "wallet", another is "mining"... (soon there will be a category "servicenodes", etc..)

Each mainmenu has its submenu section (that looks similar to the former "tabs")

We need this additional structure because there are a lot of new "tabs" coming our way soon. (we can't fit them all in the tabgroup the way we got used to, it would look ugly and unordered.)

Yes.


No.

You can explain the new features of the wallet.
I'll have it finished this week for sure. But it could get saturday/sunday.

Excellent work, I hope to see more and more tutorials from you!

Hey NoobKid, I was expecting you to show up sooner or later.

I don't know what happend to MyFarm, I guess he is still active but not interested in SpreadCoin ATM.

Masternodes?

Yes, we are still working on Masternodes!

I will release a new qt wallet with new features later this week.
After that I will need 2 weeks to prepare the first testnet servicenodes version. (so we are still +- 1 week within schedule)

I will make the testnet version completely separated from mainnet spreadcoin. (as if it were a new different coin, and not testnet of main.)
So there is no danger that you can mess up mainnet and testnet files. You will even be able to run mainnet and testnet side by side.

I appreciate the help you are offering, but I don't think we will need it ATM, because my goal is already to make the testing sessions very easy and accesible.

I am sorry, but spreadcointalk will be down for a few hours,
I need to fix something.

Will be back in no time.

I think we will sooner see an FPGA release for X11 coins, before we will see FPGA in SpreadX11.

I had wrong priorities for much too long!

(mining and trading, instead of learning and developing)

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...

Put this in your conf file:


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

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.

Certainly,
the earlier we start fleshing out ideas the better.
Brainstorming should be a constant process.

So, if you had to summarize the results of the survey you did, what would you say was the gist of it?
Escrow and Crowdfunding?

or what would be the thing that interests you most

I found building on linux to be the easiest,
building on mac just a little bit more difficult,
but building on windows by far the most inconvenient.  

But don't give up, you'll be making yourself a lot of gins until you figure it out eventually.

Thanks to mrcashking for transferring admin rights of official facebook site to me:

https://www.facebook.com/Spreadcoin

I have nothing against continuing the last mn-test session, but let's make the necessary adjustments to improve it:

https://github.com/spreadcoin/spreadcoin/blob/mn-test/src/masternodes.h

We need to increase the amount of static const int g_MaxMasternodeVotes = 10;
to something higher, say static const int g_MaxMasternodeVotes = 100;

This will make masternodes get elected and deelected faster, because it will allow 100 votes to be registered every block, and not only 10.
so that we don't need to wait days and days like last time.

Or do you propose other parameters?

I can create linux, win and mac wallets for this test round.

EDIT: Keep in mind that the service nodes I am working on have little to do with how mr. spread has implemented them here.
But that shouldn't stop us from reigniting the test net activities.  

mrcashking contacted me.

He is about to transfer the admin rights to the facebook site over to me,
because he has no time anymore to run it.

What a cool guy, I hope the transfer goes well.