[ANN][CRW] CROWN (MN-PoS) | Platform | NFT framework | Governance | Masternodes

[TwistMaister]

I have set up 2 systemnodes 6 days ago and still didn't get any rewards. System nodes are enabled and started in my wallets. What could be wrong?
This is my crown-cli getinfo

    "version" : 120300,
    "protocolversion" : 70051,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "blocks" : 1665393,
    "timeoffset" : 0,
    "connections" : 19,
    "proxy" : "",
    "difficulty" : 13586308371.08908653,
    "testnet" : false,
    "keypoololdest" : 1512500620,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""

What does

Code:

crown-cli systemnode status

return on your VPS

[thb87_v]

{
    "vin" : "CTxIn(COutPoint(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, 1), scriptSig=)",
    "service" : "xxx.xxx.xxx.xxx:9340",
    "pubkey" : "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "status" : "Systemnode successfully started"
}

I have removed IP / pubkey / systemnode outputs because I don't know if it is ok to share in public.

[stonehedge]

{
    "vin" : "CTxIn(COutPoint(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, 1), scriptSig=)",
    "service" : "xxx.xxx.xxx.xxx:9340",
    "pubkey" : "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "status" : "Systemnode successfully started"
}

I have removed IP / pubkey / systemnode outputs because I don't know if it is ok to share in public.

Nothing is wrong, payments should start any time now. The queue for first payment is about 6 days due to the number of new system nodes that have been set up. After your first payment, payments will arrive much more regularly.

[thb87_v]

Thanks for the answer stonehedge.

[CHAOSiTEC]

i dont know who owns 125MacSTmP1GY1TTiXcYJP3Eq6ZNTCojxy or 1157vNU6Fnd5xVHqnKoCT4z5Jy2zEeUKuH but i accidentially send 1x 500 to the first one (a masternode owner i helped at some point) and 2x 500 to the other one who is also a masternode owner
please return the coins to 1CUeDmYn4RWEpxs8wbKUQSYEPgRitAJ4UQ

recievers have been identified - thanks for returning the coins

[givyzyt]

Crown SystemNodes (CRW) Stats Live on Masternodes.pro

Congratulation

[Vivacia]

I have translated all of the annoucements and updates for the last 1.5 months to Dutch!

For those who are intrested:
https://bitcointalk.org/index.php?topic=2397445.new#new

I will translate them from this point on. If you feel like earning some crown (50CRW )yourself then ask the team which language has not yet been done, and start translating

[higherbridge]

I have translated all of the annoucements and updates for the last 1.5 months to Dutch!

For those who are intrested:
https://bitcointalk.org/index.php?topic=2397445.new#new

I will translate them from this point on. If you feel like earning some crown (50CRW )yourself then ask the team which language has not yet been done, and start translating

Nice work!

[urban_idler]

As the CRW team develops different uses for the system -- it's a platform that includes a "wallet" (functionally limited client software), and 2 layers of servers with a few thousand nodes....

As uses for this cloud are developed, or just connected and permissioned -- it might be that simple.....  then it is worth thinking about what would drive "sustainable value" -- and by sustainable value I am really referring to patterns which can be repeated and which compound such that you can get compounding growth which is supported by the system itself.  In financial mathematical terms this is the Du Pont Equation... 

If the platform is able to deliver uses to people at a cost which is less than what the uses are worth to people -- then the system will be creating wealth, and it would be sustainable. 

This is why for every project, it is all about the uses which can be created.

I would argue that what CRW has built is a sort of organic cloud compute resource which now just needs to be opened up for use in some fashion.  The fact that CRW conceives of the nodes as a "cloud" and as a "resource" and that the systems has a differentiation between the client and server layers is itself interesting. 

feels like the next big opportunity once the cloud is turned on for use will be to evolve the client software.  because the "client" software -- which is really the iOs and the Android apps -- should be able to access applications through the CRW cloud.... or whatever the team decides to call it. 

The goal of every business is to maximize their TAM -- or target addressable market.  The TAM for CRW is anyone who uses the cloud and a smart phone to live their life -- and then to give creative people everywhere an opportunity to develop and distribute and collect payment for their software and services on that platform.  very simple.

looking forward to seeing it all come together.

[Snoops]

There is a new Crown Vlog naming contest on twitter. The new bounty for the winner is 100 CRW. Check it out! https://twitter.com/CrownPlatform/status/940929849195147264

[pickyguttural]

I think you should add it in the thread more details concerning technology

[crowncoin_knight]

I think you should add it in the thread more details concerning technology

The new road map with more details on what we are building / specific releases will be announced next Thursday 21st of December.

[TwistMaister]

New video out!

Always wanted to know how exactly the nodes are queued and how the rewards get distributed among them?

Check this out:
https://youtu.be/PlzpXJgNF1E

[vic_crown]

Great timing for a Crown presentation in Santander, Spain on 28th of December. The G-ME-CROWN kickstarter video plus the road map released next week. Fantastic!

[TwistMaister]

As the CRW team develops different uses for the system -- it's a platform that includes a "wallet" (functionally limited client software), and 2 layers of servers with a few thousand nodes....

As uses for this cloud are developed, or just connected and permissioned -- it might be that simple.....  then it is worth thinking about what would drive "sustainable value" -- and by sustainable value I am really referring to patterns which can be repeated and which compound such that you can get compounding growth which is supported by the system itself.  In financial mathematical terms this is the Du Pont Equation... 

If the platform is able to deliver uses to people at a cost which is less than what the uses are worth to people -- then the system will be creating wealth, and it would be sustainable. 

This is why for every project, it is all about the uses which can be created.

I would argue that what CRW has built is a sort of organic cloud compute resource which now just needs to be opened up for use in some fashion.  The fact that CRW conceives of the nodes as a "cloud" and as a "resource" and that the systems has a differentiation between the client and server layers is itself interesting. 

feels like the next big opportunity once the cloud is turned on for use will be to evolve the client software.  because the "client" software -- which is really the iOs and the Android apps -- should be able to access applications through the CRW cloud.... or whatever the team decides to call it. 

The goal of every business is to maximize their TAM -- or target addressable market.  The TAM for CRW is anyone who uses the cloud and a smart phone to live their life -- and then to give creative people everywhere an opportunity to develop and distribute and collect payment for their software and services on that platform.  very simple.

looking forward to seeing it all come together.

Exactly - build something useful that is used and generates value for its users..

[j4y_naKomodo]

_________________________________________________

***  ALERT * WATCHONLY-GUI BUG * ALERT ***
____________________________________________

Greetings, friends at Crown! As Komodo Platform has been working around the clock to fine-tune the multiple GUI's that are the face of our Agama multiwallet and BarterDEX atomic swap protocols, there have obviously been many bugs found and many debugged. However, one bug in particular was found not only in our Agama GUI wallet, but also in the zcash4mac GUI swing wallet. It is a simple bug, but it warrants your attention. This is a potential money cost bug.

Crown (CRW) - As a Bitcoin-protocol cryptocurrency, your GUI wallet(s) may be susceptible to this bug.

ISSUE: 'watchonly' addresses appearing as your own in GUI wallet; users could potentially send funds to the address, unaware it is not theirs or available for withdrawal.  You can import <any address> and it becomes a 'watchonly' address. The GUI will display the address as yours, add its funds to your balance, and accept deposits, but cannot be withdrawn. This could be a normal address, my address, a p2sh address, satoshi's address, etc. This can be confusing to an end-user and will lead to many headaches for the developer, as is always the case with misplaced funds.

FOUND: in Komodo Platform's Agama multiwallet (fixed) and zcash4mac GUI swing wallet (@jl777b: "newest QT wallet seems ok about watch only, but not sure of older and when it was fixed")

ex. @grewalsatinder found the bug in his zcash swing wallet: https://i.imgur.com/sVd0QTL.png

"satinder used zcash4mac, ie. the zcash osx GUI, not ours... the assumption is no GUI out there properly handles watch only addresses, until proven that they do... agama also had this bug, which we found and fixed, so it seems a very common bug to have"

SOLUTION: For the 'watchonly' address or any address not yours, the value 'ismine' returns false. Any such address gets filtered out.

QUESTIONS:

• How does your recommended GUI deal with watchonly addresses?
• Does your GUI display watchonly addresses as different than actual addresses in the wallet?

We need to experiment a bit to see which approach gets a better response triggering the bug. People WILL lose money if they send funds to a watchonly address.

"the t3 addresses in the 'Own Addresses' column! and they absolutely cant be as they are p2sh addresses. it is clear proof that the bug is very real and anybody that understands a p2sh address will understand it cant be something in your wallet. it is usually a multisig address, so only if it is a 1of1 multisig (possible but very silly) can you have a p2sh address that is spendable, but the wallet wont even know it... normal addresses can also be watchonly, which makes this even worse. in that case it would appear in the list of addresses just like all the others. even if you are able to spot p2sh addresses visually, it wont be enough"

I've been tasked with spreading awareness and facilitating discussion of this bug, so please let me know if you have any questions. I'll get you some answers and we can minimize the impact. We wanted to reach out directly to the developers of the 60+ coins featured on Agama and BarterDEX as the bug may have a direct impact on you (via your own GUI wallet).

- Jay

[crowncoin_knight]

Great timing for a Crown presentation in Santander, Spain on 28th of December. The G-ME-CROWN kickstarter video plus the road map released next week. Fantastic!

Vic thanks for your support in Spain, Santander is home to one of the largest banks in the world, Banco Santander,  awesome that you guys are holding a presentation so close to them. Maybe they will notice Crown soon too 

[stonehedge]

_________________________________________________

***  ALERT * WATCHONLY-GUI BUG * ALERT ***
____________________________________________

Greetings, friends at Crown! As Komodo Platform has been working around the clock to fine-tune the multiple GUI's that are the face of our Agama multiwallet and BarterDEX atomic swap protocols, there have obviously been many bugs found and many debugged. However, one bug in particular was found not only in our Agama GUI wallet, but also in the zcash4mac GUI swing wallet. It is a simple bug, but it warrants your attention. This is a potential money cost bug.

Crown (CRW) - As a Bitcoin-protocol cryptocurrency, your GUI wallet(s) may be susceptible to this bug.

ISSUE: 'watchonly' addresses appearing as your own in GUI wallet; users could potentially send funds to the address, unaware it is not theirs or available for withdrawal.  You can import <any address> and it becomes a 'watchonly' address. The GUI will display the address as yours, add its funds to your balance, and accept deposits, but cannot be withdrawn. This could be a normal address, my address, a p2sh address, satoshi's address, etc. This can be confusing to an end-user and will lead to many headaches for the developer, as is always the case with misplaced funds.

FOUND: in Komodo Platform's Agama multiwallet (fixed) and zcash4mac GUI swing wallet (@jl777b: "newest QT wallet seems ok about watch only, but not sure of older and when it was fixed")

ex. @grewalsatinder found the bug in his zcash swing wallet:

"satinder used zcash4mac, ie. the zcash osx GUI, not ours... the assumption is no GUI out there properly handles watch only addresses, until proven that they do... agama also had this bug, which we found and fixed, so it seems a very common bug to have"

SOLUTION: For the 'watchonly' address or any address not yours, the value 'ismine' returns false. Any such address gets filtered out.

QUESTIONS:

• How does your recommended GUI deal with watchonly addresses?
• Does your GUI display watchonly addresses as different than actual addresses in the wallet?

We need to experiment a bit to see which approach gets a better response triggering the bug. People WILL lose money if they send funds to a watchonly address.

"the t3 addresses in the 'Own Addresses' column! and they absolutely cant be as they are p2sh addresses. it is clear proof that the bug is very real and anybody that understands a p2sh address will understand it cant be something in your wallet. it is usually a multisig address, so only if it is a 1of1 multisig (possible but very silly) can you have a p2sh address that is spendable, but the wallet wont even know it... normal addresses can also be watchonly, which makes this even worse. in that case it would appear in the list of addresses just like all the others. even if you are able to spot p2sh addresses visually, it wont be enough"

I've been tasked with spreading awareness and facilitating discussion of this bug, so please let me know if you have any questions. I'll get you some answers and we can minimize the impact. We wanted to reach out directly to the developers of the 60+ coins featured on Agama and BarterDEX as the bug may have a direct impact on you (via your own GUI wallet).

- Jay

Thanks for the warning Jay, I'll make sure the right people see it.

[j4y_naKomodo]

_________________________________________________

***  ALERT * WATCHONLY-GUI BUG * ALERT ***
____________________________________________

Greetings, friends at Crown! As Komodo Platform has been working around the clock to fine-tune the multiple GUI's that are the face of our Agama multiwallet and BarterDEX atomic swap protocols, there have obviously been many bugs found and many debugged. However, one bug in particular was found not only in our Agama GUI wallet, but also in the zcash4mac GUI swing wallet. It is a simple bug, but it warrants your attention. This is a potential money cost bug.

Crown (CRW) - As a Bitcoin-protocol cryptocurrency, your GUI wallet(s) may be susceptible to this bug.

ISSUE: 'watchonly' addresses appearing as your own in GUI wallet; users could potentially send funds to the address, unaware it is not theirs or available for withdrawal.  You can import <any address> and it becomes a 'watchonly' address. The GUI will display the address as yours, add its funds to your balance, and accept deposits, but cannot be withdrawn. This could be a normal address, my address, a p2sh address, satoshi's address, etc. This can be confusing to an end-user and will lead to many headaches for the developer, as is always the case with misplaced funds.

FOUND: in Komodo Platform's Agama multiwallet (fixed) and zcash4mac GUI swing wallet (@jl777b: "newest QT wallet seems ok about watch only, but not sure of older and when it was fixed")

ex. @grewalsatinder found the bug in his zcash swing wallet: https://i.imgur.com/sVd0QTL.png

"satinder used zcash4mac, ie. the zcash osx GUI, not ours... the assumption is no GUI out there properly handles watch only addresses, until proven that they do... agama also had this bug, which we found and fixed, so it seems a very common bug to have"

SOLUTION: For the 'watchonly' address or any address not yours, the value 'ismine' returns false. Any such address gets filtered out.

QUESTIONS:

• How does your recommended GUI deal with watchonly addresses?
• Does your GUI display watchonly addresses as different than actual addresses in the wallet?

We need to experiment a bit to see which approach gets a better response triggering the bug. People WILL lose money if they send funds to a watchonly address.

"the t3 addresses in the 'Own Addresses' column! and they absolutely cant be as they are p2sh addresses. it is clear proof that the bug is very real and anybody that understands a p2sh address will understand it cant be something in your wallet. it is usually a multisig address, so only if it is a 1of1 multisig (possible but very silly) can you have a p2sh address that is spendable, but the wallet wont even know it... normal addresses can also be watchonly, which makes this even worse. in that case it would appear in the list of addresses just like all the others. even if you are able to spot p2sh addresses visually, it wont be enough"

I've been tasked with spreading awareness and facilitating discussion of this bug, so please let me know if you have any questions. I'll get you some answers and we can minimize the impact. We wanted to reach out directly to the developers of the 60+ coins featured on Agama and BarterDEX as the bug may have a direct impact on you (via your own GUI wallet).

- Jay

Thanks for the warning Jay, I'll make sure the right people see it.

Excellent! Thank you.

[vic_crown]

Great timing for a Crown presentation in Santander, Spain on 28th of December. The G-ME-CROWN kickstarter video plus the road map released next week. Fantastic!

Vic thanks for your support in Spain, Santander is home to one of the largest banks in the world, Banco Santander,  awesome that you guys are holding a presentation so close to them. Maybe they will notice Crown soon too 

The G-ME collaboration is going to push us big time here in Spain. And this is just the beginning, next month we will announce a new project in another real use case for the Crown blockchain.