Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 153. (Read 317079 times)

The network is looking super stable regardless

Bigmo -- thanks for you comments and looking forward to discussing on slack.

NOTARY / REGISTRATION / UTILITIES
Regarding the Notary service - there are different elements of this.  What we traditionally think of as a notary doesn't quite apply -- what we really need is a method of registering an address as being owned by a specific individual or entity in a specific legal jurisdiction.  For a crown address to be able to engage in certain transactions, it is likely that it will need to be registered in this fashion.  But if an address is registered - or there is a legal chain of title for the ownership of the address in a specific legal jurisdiction, then it is not a huge leap to the owner of the address using that account to hold title to other assets.

Also -- since the Crown Addresses are formed following the same format as Bitcoin, and other alt-coins use this as well -- and one value of the address system is non-collision -- well then a registered Crown Address could also (de facto) be the registration of the address for other blockchains using the same protocol... there's a missing step in there but I think it can be figured out.  But the address protocol matching Bitcoin is probably important here.... and easy to forget.

In terms of how one would implement a "registration" system, or notary -- you probably know more than we do... but part of the idea of creating a (1 by X) matrix of mutable keys in each address (skeleton keys) -- is to create options.  A skeleton key could map to an address in a registrar's blockchain, or database... or it could be a key to a lockbox containing information, or just a hash of the registrar's info and the registrant's name address and tax id, which are confirmation of who the registrar is, who the registrant is.  No sure what implementation would make the most sense.

But as Defunctec said -- this is an important feature which we will need.  Once individuals and corporations can take title to an address in a clear, irrefutable way -- then we clear the way for addresses being no different than other accounts in some ways, in that they should be able to also "hold" other assets, and you start to get to being able to legally represent and trade between these registered addresses. 

This registration service will not be a function which the Crown Core will "do" -- independent businesses will need to be set up handling this function in different legal jurisdictions.  The Core Team does have an interest in helping standardize how addresses are registered, and having this be a standard utility function available on the Crown Platform, with the registration information -- a hash of or a key to,  permanently stored on the blockchain.  You can see in one of the papers how we are thinking about this.  One essential feature of what the core team will seek to do is not to be in the business of offering services on the Crown Platform -- but to be in the business of increasing the value and usefulness of the platform.  This means that we will seek to promulgate (share and distribute) what we see as best practices, and also suggest preferred ways of registering addresses or other things.  The benefit of having "best practices" or "preferred methods" is in having a way of doing something -- like registering addresses, achieve economies of scale.  That said -- our suggested best practices are likely to just follow what successful businesses implement using the capabilities we embed in the new Crown Core...

There is a whole suite of "utility" functions or applications, like address registration -- which will be a top priority to develop, and which we will be looking for early partners to work with us as we build the new Crown Core, so that ideally they will be ready to be released with the new Core... but that's just another dream at this point....   

Thanks for your interest -- as stated before, this only works if other see the value and see a way to do cool stuff with it and also make some money to pay the bills.

   

 

IF you are mining on the old client now, I advise that you upgrade ! blocks from pre 0.12 are no longer being accepted with throne enforcement coming online so quickly.

I've been SEARCHING for a solution for this. and it is in my plans to figure out the exact issue. but it comes down to the way the block headers are prepared for ppc vs crw

No. of Trons under new client slowly going up

auxminingaddr=1FHTZYz7M9SwEw1122CzH4GvGj6s8bPLhU

So far, all my tests came out good, https://mergemining.com is running latest CRW daemon now.

As a side note, I'm willing a lot of people on linux are going to get bit with the name change. Daemon name changed from crowncoind to crownd ... Don't forget to update your scripts

That message is to be expected until a few more people update their nodes.  Just leave it running, it should resolve as more updates happen.

Ok, thanks for your answers.

I have managed to download and sychnronize the whole block chain which has around 6GB now.
Anyway now I´m getting synchronization failed error while synchronizing additional data at 50% of the progress.
The progress bar says... syncing sporks, syncing thrones and then it gives the sync. failed error.
I will try to reindex the wallet again and will see what happen. I´m on Win10 using 64bit version.

yes.. these "big" transactions have quite a high fee ( up to 5% )...
i used "settxfee" wrong.. ( thought it was in CRW not in CRW/kB )

great to see the progress here. i will give you pool statistics soon. but can you answer me one question:

are there some coins not possible as "parent coin" for merged mining?
it seems that POS-coins will not work (PPC, DEM). the block is valid in the parent chain, but crownd  says:

is this a general problem or might thete be a problem with my implementation?

1. Darksend, we will take it out
2. Good point, we will change the color of teh logo in the windows icon on taskbar
3. Infernoman took the Throne tab out, since the tab was not useful there. you set up thrones through a vps anyway. @infernoman?

double check they are updated, check output from "throne outputs" if the txid and vout are correct in your throne.conf

Hi

After windows wallet update when i try to start throne i get error: Not capable throne: Could not connect to xxx.xxx.xxx.xxx
I updated linux vps server too, but nothing changed...

Bigmo thanks for your comments!

1. Trezor and slushpool - yes push them if you have the opportunity to help this

Yes, there is definitely few areas how I can help. Lets dicuss this on slack.
2. Notary service - this feature is a very important one, I would like to see it running on Crown. Who will make it happen?  

I´m aware of it and thats way a pointed out this feature. Lets discuss on Slack
3. Logo - good idea, pls take it from here http://crown.tech/history scroll to the bottom, anything else you need?

Ok, I will try to use the logo from there.
4. Thrones on a browser - we will discuss in the team, for me it is a good idea! Ok, cool. I think this definitely think to atleast considerable to think about:-)

5. SSL Certificate, this should not be a problem, the question is if this has real added value. Let me look into it.

Well the biggest added values are as Stonehedge mentioned. You are building application platform with the highest level of security on the market so you should show to everyone that security is your top priority.


Defunctec - no problem I´m happy to help where I can. Looking forward to be added on slack and discuss this is details.


I´m syncing the QT now. The UI looks great and it is definitely good step forward from the bitcoin qt UI.

Just 2 quick comments before I sync the wallet and will be able to test it.

1. In Transaction history tab when you want to sort trans. there is Darksent text left which remains the wallet has being cloned from Dash it is not a big issue not at all but good to think to update the text with some next wallet release.

2. Second think is the logo with the light blue color is hardly visible as a windows icon on taskbar. It is not a big issue again but people with worse vision could have problems:-)


3. Why does Windows QT client does not include Thrones tab which has being showed in the screenshots before?

No problem, let us know if you need any help.

Just updating my Thrones.  New wallet seems really stable on my remote servers but having problems with my local dev server.  Probably an environment issue though, trying to work it out now.

Oh no problem, I'm appreciative of all the advice I've received. I'm hopeful I can carve out a little time Wednesday to download the new wallet and give it another shot through a vps instance. The new design looks fantastic and along with the recently released whitepaper, shows a strong commitment from the crown staff.

When you update please add auxminingaddr= to your crown.conf and if you could post that address it would be greatly appreciated. We would like to figure out the block distribution for as many pools as possible.

Node-vps.com will update the daemons over the next 48 hours

I've updated the Thrones tab with a new Windows/linux vps setup guide and Infernomans Throne income calculator.

[THRONES]

Great news, thank you!
Let us know the results of your test's