I just wrote down all Facebook likers (110 stakes), Twitter followers (302 stakes), Newsletter subscribers (955 stakes), Signature participants (93 stakes) and translators (27 stakes).
Week #1 Values
Please note that there is an unusual high number of newsletter subscribers. We suspect that these are fake emails. We are using Mailchimp to send out our newsletters, and we can see user ratings there. That means we can see if a user is reading a newsletter or not. At the end of the newsletter bounty campaign we can filter out all fake emails this way.
Here you can view the signature stakes for the second week. The other lists won't be released, because there exists a privacy conflict.
Thank you very much.
I can't see me on these sig stats?? please can you review this. thanks.
I will add you, as I know that you added it before. Seems like your signature slipped through. Even though I wish you would make it more beautiful. I know the life as a "newbie" rank member is hard here.
Tomorrow you will find yourself on this list for week 2.
thanks very much I am following this project keenly. I am actually a hero member but they hacked my account. theymos is hopefully going to give it back to me soon.
another question is i don't have any facebook or social media since my gf deleted it all and changed the emails. Can i get credits for getting other people to give facebook likes and messaging you?
Sorry to hear that. Wish you the best!
You can't get bounty stakes for other people you convinced to like/follow Lisk. Sorry.
I am reading Whitepaper and Developing section (https://lisk.io/documentation?i=lisk-dapps-docs/README) now.
But I don't find a way to prevent dapps from change by owner.
As example: someone created list-btc exchange dapp. Customers inspect the source of dapp and
don't find something worried. Code is clear and safe. They send funds (lisk, btc) to dapp.
Can dapps owner change the dapp code and steal the funds?
What will happen with the funds If the dapp stops working?
Are there some way to prevent dapp from change by owner?
Can I create a trustful dapp secured by mainchain?
By tomorrow I have updated the whitepaper.
"Dapp owners": Is the person who developed the decentralized application and I presume he also has at least 1 master node running. (WRITE/READ)
"Dapp master node": One of maximum 101 sidechain forgers. (WRITE/READ)
"Dapp user": Regular user who is simply running the dapp. (READ-only)
Let's say in our scenario there are 101 sidechain master nodes, this is the best case and equals Lisk itself. There are now different scenarios.
Dapp owner changes the source code on e.g. GitHub: This can be seen as a regular update for the dapp, either soft or hard fork. Similar to an update for crypto-currencies. The network itself isn't affected as long as nodes don't update.
Dapp owner/any master node owner changes only the source code on his own master node: Here it matters where he made the changes. If the changes are in non-critical areas (I can't define the critical areas in general, e.g. a critical area is block generation, a non-critical is frontend) nothing happens and he can still participate as a sidechain forger. However, if a critical area is affected his generated blocks won't be accepted by the sidechain and he will land on a fork. The whole network won't fork here, only his own node.
Many master nodes update to latest hard fork version:
x nodes: There will be two networks active. One on the majority and one on the minority of the master nodes. Users will have to choose which fork they chose.
nearly all nodes: A huge majority inherently decides which fork is the "main" path. Therefore this can be seen as a hard fork which may occur with regular updates. (e.g. at Bitcoin the increase of Block size)
Many individual dapp users change their dapp: Nothing happens to the network itself, because these users don't generate new sidechain blocks.
So, in conclusion this is exactly the same behaviour as in crypto-currencies like Bitcoin or Nxt. If a dapp owner wants to introduce new features he should do it with milestones, that means at a certain blockchain height the new feature will be activated. This way the master nodes have a certain timeframe to switch to the update (or may decide against it).
LiskHQ , the 101 top lisk wallet adresses that make a node will become delegates right ?
Can there be a way that the Lisk team will claim up all of those delegates , cause with the millions coins even split in 101 wallets they will have the top wallets or am i thinking wrong ?