[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS

[50cent_rapper]

I wouldn't mind if you enable anonymous comments under blog posts.

Google likes very much (in terms of SEO) unique content, regual updates and comments under this content.

[dzarmush]

A little more patience. Let's wait for 0.4.0 version with DappStore and custom chains - only 45 days to wait.

Is there a road map? I haven't seen any particular timing.

[Passion_ltc]

Max, your dapp overview is very good and still has me thinking.  

Is it possible to write the XCR code so master dapp nodes have an adjustable time (longer that 10 seconds) to perform side chain block addition?   Say a dapp author was OK with modifying the side chain every 30 seconds or once a minute.  This would probably overcome the latency problem that disqualified using home PCs / Raspberry Pis on slow home networks that were not hooked up to an internet backbone.   The ability to run master dapp nodes and side chains on $35 Raspberry Pi 2 quad-core computers at home instead of just at expensive server farms would be a big plus to Crypti.   Many more users would try to run Crypti dapps if it could be done on cheap computers running on home networks.  We had hoped to do this with the 10 second XCR main chain and it didn't work.  We should try to make this a possible option on dapp side chain master servers.  

A second thought - maybe we should do a whole new [ANN] announcement here on BTC for XCR dapps, to let people know that XCR has revolutionary new capabilities beyond the typical cryptocurrency.  

You will be able to use Cryptis or Bitcoin consensus. That means either 10s or 10m. But I think Boris mentioned once, that you can also use only every 10th Crypti block or so, making the block time 100 seconds effectively.

Regarding the second thing, we will when we release it. I think it's more important to market outside of BitcoinTalk, because we want to build the platform with many dapps creating value (=price) this way. We don't want to pump the price with announcements within the Bitcoin community.

I wouldn't mind if you enable anonymous comments under blog posts.

Google likes very much (in terms of SEO) unique content, regual updates and comments under this content.

Is there a quick way to do this with Ghost (blog software)?

A little more patience. Let's wait for 0.4.0 version with DappStore and custom chains - only 45 days to wait.

Is there a road map? I haven't seen any particular timing.

I don't know why 50cent_rapper has these 45 days in mind. But we have a roadmap, check the OP. Here is the detailed one: https://docs.google.com/spreadsheets/d/1Zzsu0BikplztWB8xTU3PhMHbyHBrW8EX3lR-e6lS8LA/pubhtml

I probably need to explain it,

Multi-signature: The backend is done. The frontend will be finished this month. But, this is a feature which will probably be used by <1% of our users, therefore we will release it together with the dapps in v0.4.0. Else we would need to test everything again and the releases will be pushed further behind.

Dapps Virtual Machine: All dapps will run in a virtual machine (I hope you guys read the white paper. ), this functionality is done already. But this is only a part of the dapps, there are many more things which are done, but also many more things which need to be done.

Sidechains: Formerly we always used the term "Custom Blockchain", but the majority inside the cryptocurrency community call it sidechains. Therefore we changed the term for ourselves as well. They will act like decentralized databases for the dapps.

Avatars/Messages: These will be implemented as dapps, we don't want to pollute Crypti's main chain with them.

Also the sheet just talks about the crypti core/backend. The frontend is running seperately, sometimes it's finished much sooner, sometimes it takes 1-2 weeks longer. Also the public beta versions and test phases are not included in the roadmap, we will have to dramatically test the dapp functionalities.

[patmast3r]

Can someone explain to me what it is about cryptis dapps that is actually decentralized ? From what I gathered one person owns the app and it relies on that same person to run masternodes. Am i missing something ? Did i missunderstand that part ?

This is an honest question. I don't mean to hate. Just asking a question.

[50cent_rapper]

I don't know why 50cent_rapper has these 45 days in mind. But we have a roadmap, check the OP. Here is the detailed one: https://docs.google.com/spreadsheets/d/1Zzsu0BikplztWB8xTU3PhMHbyHBrW8EX3lR-e6lS8LA/pubhtml

Damn. I have had this in mind because yesterday the roadmap were different. So you updated it few hours ago and then say like "I don't know why 50cent_rapper has these 45 days in mind". You have a sence of humor

Well new roadmap says DappStore will be in october  

[Passion_ltc]

Can someone explain to me what it is about cryptis dapps that is actually decentralized ? From what I gathered one person owns the app and it relies on that same person to run masternodes. Am i missing something ? Did i missunderstand that part ?

This is an honest question. I don't mean to hate. Just asking a question.

A dapp consists of several parts:

- storage of dapp files

Here we have two choices, one centralized (GitHub), but also a 3rd party decentralized method. The decentralized method can't be disclosed yet, but as you probably know there are several options on the market. At the beginning it will be one of them, and later we will add the others step-by-step. Maybe even an in-house solution will be coded as a dapp later by some developer.

- computation of the dapp

While a centralized application relies on a single server to perform it, we have 16 master nodes. This number will be raised in the future, but we will begin with 16 for now. If you are a dapp owner you can now look for 15 other independent persons, who can help you run your dapp.

- hosting of the dapp

Where is the difference between hosting and computation of a dapp? A normal server usually takes care of both, a master node at Crypti takes care of both as well. But an unlimited number of full nodes can install and start the dapp as well, so other users (lite client, mobile client) can access it though them.



Let's make an example, our example case will be a Bitcoin dice gambling game.

The team consists of 3 persons; a CEO (C), a technical guy (T) and a marketing guy (M).

Centralized (worst case):

The centralized service now has 1 server running for the website and C has access to the fundings.

- website hacked: All funds are stolen, the users will not get reimbursed.
- server down: The users don't have access to their funds.
- C runs away: The users lost all their money.


Centralized (good case):

The centralized service now has 3 servers running for the website and C, T and M have access to the fundings, within a multi-signature account in the cold wallet.

- website hacked: The hot wallet got emptied, users will maybe get reimbursed.
- servers down: The users don't have access to their funds.
- 2-of-3 admins run away: The users lost all their money.

You see, the good case is much better already. Now the advantages/disadvantages between centralized <-> decentralized services come into play. They already use a multi-signature account, but the servers can still go down.


Decentralized:

The decentralized service is running on 10 master nodes and 20 full nodes. C, T and M have 1 key each. But they also asked 4 delegates of the Crypti network, 1 Crypti foundation member and 1 escrow person to hold keys. This can of course also be done with a centralized service, but at Crypti there is automatically a verification of this possible.  Also it's inbuilt, resulting in a lot lower work for the site admins.

- website hacked: Well, the website can't get hacked. The only thing which can get hacked are the master node keys for Crypti and the decentralized hosting solution. Hot wallets might get emptied, but if the multi-signature implementation into the dapp got properly done, it's nearly impossible to do so.
- servers down: For this all 10 master nodes need to get DDOS'ed. This is of course possible, therefore the dapp owner could raise it to 16 master nodes. Later we will raise this number, so a dapp can get computed by for example 100 nodes. But the master nodes only take care of the database operations, for only viewing the site there are still many more full nodes. If you run your own full node to access the service, you will most certainly always have access.
- admins run away: Thanks to the multi-signature it's not possible. Again, this can be done in a centralized website as well. But at Crypti it's automated and checkable.

Along side these, the dapp is running on a sidechain. Here comes the regular blockchain technology advantages into play now. Everyone can check the liquidity of the service, can check the transactions on the sidechain and so on.

Crypti will also offer many more advantages, like
- an inbuilt token system (similar to the Nxt asset exchange, only for the dapps).
- APIs for Crypti and Bitcoin implementations.
- libraries and developer tools.
- a Dapp Store, making the dapps accessable from anywhere and from everyone.


I hope this explanation helps. I might have missed some things, even I can't imagine yet.

[Passion_ltc]

I don't know why 50cent_rapper has these 45 days in mind. But we have a roadmap, check the OP. Here is the detailed one: https://docs.google.com/spreadsheets/d/1Zzsu0BikplztWB8xTU3PhMHbyHBrW8EX3lR-e6lS8LA/pubhtml

Damn. I have had this in mind because yesterday the roadmap were different. So you updated it few hours ago and then say like "I don't know why 50cent_rapper has these 45 days in mind". You have a sence of humor

Well new roadmap says DappStore will be in october  

Hey sorry, yes I changed it a bit. Normally nothing should got pushed further back, maybe I made a mistake editing them or you saw a cached version. I will let Boris take a look over it and update the dates accordingly. I'm pretty sure it's not correct at every point.

I will tell you, when you can take a look again.


Edit: I see now, multi-sig is done already. But I pushed it back to be in one line with the sidechains and dapp VM as they will get released together. Avatars/Messages will be released once the store and everything is finished, bc they will actually get implemented as a dapp. About "Compute nodes integration", "Storage nodes integration" and "3rd party chain integration (BTC, etc...)" I just asked Boris. Let's wait for his opinion.

[50cent_rapper]

Can someone explain to me what it is about cryptis dapps that is actually decentralized ? From what I gathered one person owns the app and it relies on that same person to run masternodes. Am i missing something ? Did i missunderstand that part ?

This is an honest question. I don't mean to hate. Just asking a question.

A dapp consists of several parts:

- storage of dapp files

Here we have two choices, one centralized (GitHub), but also a 3rd party decentralized method. The decentralized method can't be disclosed yet, but as you probably know there are several options on the market. At the beginning it will be one of them, and later we will add the others step-by-step. Maybe even an in-house solution will be coded as a dapp later by some developer.

- computation of the dapp

While a centralized application relies on a single server to perform it, we have 16 master nodes. This number will be raised in the future, but we will begin with 16 for now. If you are a dapp owner you can now look for 15 other independent persons, who can help you run your dapp.

- hosting of the dapp

Where is the difference between hosting and computation of a dapp? A normal server usually takes care of both, a master node at Crypti takes care of both as well. But an unlimited number of full nodes can install and start the dapp as well, so other users (lite client, mobile client) can access it though them.



Let's make an example, our example case will be a Bitcoin dice gambling game.

The team consists of 3 persons; a CEO (C), a technical guy (T) and a marketing guy (M).

Centralized (worst case):

The centralized service now has 1 server running for the website and C has access to the fundings.

- website hacked: All funds are stolen, the users will not get reimbursed.
- server down: The users don't have access to their funds.
- C runs away: The users lost all their money.


Centralized (good case):

The centralized service now has 3 servers running for the website and C, T and M have access to the fundings, within a multi-signature account in the cold wallet.

- website hacked: The hot wallet got emptied, users will maybe get reimbursed.
- servers down: The users don't have access to their funds.
- 2-of-3 admins run away: The users lost all their money.

You see, the good case is much better already. Now the advantages/disadvantages between centralized <-> decentralized services come into play. They already use a multi-signature account, but the servers can still go down.


Decentralized:

The decentralized service is running on 10 master nodes and 20 full nodes. C, T and M have 1 key each. But they also asked 4 delegates of the Crypti network, 1 Crypti foundation member and 1 escrow person to hold keys. This can of course also be done with a centralized service, but at Crypti there is automatically a verification of this possible.  Also it's inbuilt, resulting in a lot lower work for the site admins.

- website hacked: Well, the website can't get hacked. The only thing which can get hacked are the master node keys for Crypti and the decentralized hosting solution. Hot wallets might get emptied, but if the multi-signature implementation into the dapp got properly done, it's nearly impossible to do so.
- servers down: For this all 10 master nodes need to get DDOS'ed. This is of course possible, therefore the dapp owner could raise it to 16 master nodes. Later we will raise this number, so a dapp can get computed by for example 100 nodes. But the master nodes only take care of the database operations, for only viewing the site there are still many more full nodes. If you run your own full node to access the service, you will most certainly always have access.
- admins run away: Thanks to the multi-signature it's not possible. Again, this can be done in a centralized website as well. But at Crypti it's automated and checkable.

Along side these, the dapp is running on a sidechain. Here comes the regular blockchain technology advantages into play now. Everyone can check the liquidity of the service, can check the transactions on the sidechain and so on.

Crypti will also offer many more advantages, like
- an inbuilt token system (similar to the Nxt asset exchange, only for the dapps).
- APIs for Crypti and Bitcoin implementations.
- libraries and developer tools.
- a Dapp Store, making the dapps accessable from anywhere and from everyone.


I hope this explanation helps. I might have missed some things, even I can't imagine yet.

Passion_ltc what is the difference between "master nodes" and "full nodes" ?

Good post for blog by the way.

[Passion_ltc]

Passion_ltc what is the difference between "master nodes" and "full nodes" ?

Good post for blog by the way.

Check here: http://blog.crypti.me/cryptis-dapp-platform-explained/

Quick explanation: There is the dapp owner (Founder). Several people (Crypti accounts) can connect to his account, making a multi-signature account. Those will be the master nodes, because they also have rights over the funds of the dapp and they take care of the database operations. (Consensus, similar to Crypti delegates) Full nodes just make the user interface of the dapp accessable to others (and to themselves).

When I say they have rights over the funds I mean this: e.g. there are 6 accounts, you need 3 OK to transfer the funds. Check out this blog post: http://blog.crypti.me/an-introduction-to-our-multi-signature-implementation/

When I say database operations, I mean they put the transactions into the blocks, forge new blocks, taking care of consensus in the sidechain. Working similar to DPOS. http://blog.crypti.me/introduction-to-dpos/


Regarding blog post, I would need to let the team check the above. Maybe I made a small mistake somewhere, but in general it's correct.

[50cent_rapper]

Optimally 16 master nodes are running your dapp, creating a base and providing the consensus. we might raise the number of possible master nodes in the future. Additionally an unlimited number of full nodes can support the decentralized peer-to-peer network of the dapp, providing a decentralized accessing option for the lite clients.

To make a comparison; the master nodes are the backbone of the whole system making database/blockchain operations. The full nodes are acting like accessing servers, with the regular users accessing them with their lite and mobile clients.

Good design! Those "full nodes" provide "scalability" for hi-loaded dapps with million users 

[Passion_ltc]

Optimally 16 master nodes are running your dapp, creating a base and providing the consensus. we might raise the number of possible master nodes in the future. Additionally an unlimited number of full nodes can support the decentralized peer-to-peer network of the dapp, providing a decentralized accessing option for the lite clients.

To make a comparison; the master nodes are the backbone of the whole system making database/blockchain operations. The full nodes are acting like accessing servers, with the regular users accessing them with their lite and mobile clients.

Good design! Those "full nodes" provide "scalability" for hi-loaded dapps with million users 

it depends on the dapp.

If you have a heavy database driven dapp (e.g. chat service) they add very little, as only the master nodes will save the messages into the sidechain. 

If you have a service which is mostly viewing (e.g. news portal) then they add a huge scalability bonus.

[patmast3r]

...
I hope this explanation helps. I might have missed some things, even I can't imagine yet.

Thanks a lot for your detailed explanantion !

[Passion_ltc]

...
I hope this explanation helps. I might have missed some things, even I can't imagine yet.

Thanks a lot for your detailed explanantion !

Let me know if you think it's possible to make truly decentralized applications.

[patmast3r]

...
I hope this explanation helps. I might have missed some things, even I can't imagine yet.

Thanks a lot for your detailed explanantion !

Let me know if you think it's possible to make truly decentralized applications.

I don't think it is. Someone would have come up with it by now
Distributing it as much possible is as good as it gets right now and i think Crypti is doing that quite well.

[Passion_ltc]

...
I hope this explanation helps. I might have missed some things, even I can't imagine yet.

Thanks a lot for your detailed explanantion !

Let me know if you think it's possible to make truly decentralized applications.

I don't think it is. Someone would have come up with it by now
Distributing it as much possible is as good as it gets right now and i think Crypti is doing that quite well.

What do you mean? Can you elaborate?

[jiuge]

When go to space?

XCR rocket 3 2 1 Fire.

[Passion_ltc]

When go to space?

XCR rocket 3 2 1 Fire.

We are preparing the start.

[50cent_rapper]

Sure. Someone remembers the exact date of the IPO end?

Well, tomorrow, 16 juny is 1 year after IPO end. You must mention it in blog weekly update.

Raised funds update

Following my communication with Bter, they confirmed that 727.103605 were raised.
Together with Maxmint raised 33.80307572, it totals to 760.90668072!

We are now discussing with Bter the best way to proceed for the remainder of the pre-sale period, allowing both additional purchasing and refunding.
At the end of the pre-sale period, we will process the funds raised both through Bter and Maxmint, to refund these over the 750 BTC cap.


On that note, I'd like to thank again the crypto community. We are grateful that you have given us this chance, and commit to making Crypti the best and most commonly accepted eCommerce crypto possible.

[Passion_ltc]

Sure. Someone remembers the exact date of the IPO end?

Well, tomorrow, 16 juny is 1 year after IPO end. You must mention it in blog weekly update.

Raised funds update

Following my communication with Bter, they confirmed that 727.103605 were raised.
Together with Maxmint raised 33.80307572, it totals to 760.90668072!

We are now discussing with Bter the best way to proceed for the remainder of the pre-sale period, allowing both additional purchasing and refunding.
At the end of the pre-sale period, we will process the funds raised both through Bter and Maxmint, to refund these over the 750 BTC cap.


On that note, I'd like to thank again the crypto community. We are grateful that you have given us this chance, and commit to making Crypti the best and most commonly accepted eCommerce crypto possible.

Yes, lucky that it is a Thursday.

[MalReynolds]

Home PCs / Raspberry Pis on slow home networks couldn't run the Crypti main blockchain.  So, can master dapp nodes have an adjustable time (longer that 10 seconds) to perform side chain block addition?  It would be a big plus to run master dapp nodes and side chains at home on $35 Raspberry Pis instead of just on expensive server farms.    Many more users would try to run Crypti dapps if it could be done on cheap computers running on home networks.  We should try to make this a possible option on dapp side chain master servers.