Bitcoin Forum
May 24, 2024, 07:48:48 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Scalability "www.injoin.in"  (Read 289 times)
injoin (OP)
Newbie
*
Offline Offline

Activity: 42
Merit: 0


View Profile WWW
September 06, 2017, 04:16:40 PM
 #1

In previous posts(“Pool”), we have looked at the key mechanisms of injoin.
This post, let’s take a look at the scalability of injoin based on the conceptwe covered earlier.
1. Usage history station and Station network
A user uses contracts(events) in accordance with a sponsorship contract andsubmitsthe gas fee to a sponsor pool.
However, in this process, each time you use a contract, you have to submit the gas fee and the transaction address of the previous contract to the sponsor pool,which creates a lot of transactions in the sponsor pool, resulting as another gas fee.
We have created a usage history station to make this efficient. Depending on a contract, the utilizing usage history station will allow you to do hundreds of transactions with just a couple of transactions.
The Usage history station reduces the number of transactions and ultimately reduces the gas fee used when accessing the sponsor pool.
https://i.imgur.com/IQzyBTW.jpg
In the figure above, the user saves the transaction address and gas fee for theevent in the usage history station without attaching it every time to send an event(Usage history station is in the off-chain).
According to the sponsorship contract, the value of the first transaction isstored in the usage history station and the value stored in the gas station will be transferred to the sponsor pool on the n-1th transaction. After transferred to thesponsor pool, the scanner will confirm the submitted gas fee and transactionaddress, and if it matches, approve the withdrawal.
In addition to this, usage history stations are networked together so that a usage history station can collect values from other usage history stations and transmit more values at once. Depending on network size, usage history station networks are more scalable to aggregate more than existing usage original gas stations.
2. Event community and event community network
Users can connect with other users by creating an event through the injoin standard contract.
If you want to raise your own event, you should pay the gas fee and then you can receive sponsorship from the sponsor. But you can skip this process and post the event.
It is possible through the event community.
An event community defines a specific topic or community (a school, company,or village) where users upload events through the event community, and the event community uploads events for many users. When users create an event,they pay a gas fee per event, but in the event community, you can increase gas fees and transaction efficiency by collecting and uploading the events of many users.
https://i.imgur.com/UTuvuJn.jpg
As described above, by uploading your event via the event community, you can reduce the gas fee and reduce the number of transactions and have more scalability as you can upload many events created by multiple users in one transaction.
When a user send an event through the event community, the user pass his event to the event community on the offchain.
Because it is done outside the blockchain, the user can upload events withperfect anonymity, nickname ora real name. Also, event community managers (one or more administrators of the eventcommunity) can determine the event so that the event of the malicious user is blocked. Event community managers can activate their communities and get a good reputation in injoin. A well-reputed event community manager can be supported by many people when making an initiative
And these event communities can network with other event communities. Once you have a network, you can share popular events among those networks andfurther reduce network costs for event gas fee.
Users upload their own events, but sometimes users may want to create events with multiple people. Event organization is available and the event can be created and maintained persistently, not temporarily.
For example, let’s say you want to create a bazaar in your neighborhood. However, it can be difficult to do it alone. In this case,you can create an Event organization.
Participants in the event organization intervene in the specificity of the event and adjust it to materialize it.
The bazaar will continue if a bazaar is held with the expected number of people, goods, places, and a good reputation from the people.
The sponsor pool network makes a network of sponsor pools to reduce gas costs. Users can create their own sponsor pools, but sponsor pool is also a smart contract and costs fees.
https://i.imgur.com/IBZBx5c.jpg
As for one-time sponsorship activity, you can sponsor (Image 1) using anotheruser’s sponsor pool.
If the sponsor’s own sponsor pool is too small or not known, users might not use their sponsor pool, they can ask anothersponsor pool to link their sponsorpool (Image 2).
For those who have entered the larger sponsor pool, you can use the related pool.
Multiple users can create one large sponsor pool (Image 3). You can reduce thecost of creating your own sponsor pools by using other users’ sponsor pools.
We saw the scalability of injoin through the usage history station, the event community, and the event community network, the event organization, and the sponsor pool network. It is still in its infancy and functions will be added after development and release. Thank you for any questions or comments.
We welcome any questions or comments.

Smart contracts used by 7 billion people : www.injoin.in

https://i.imgur.com/LJQgjUk.png

injoin
Meduim
Reddit
Slack
Twitter
github
Youtube
christwaston
Newbie
*
Offline Offline

Activity: 89
Merit: 0


View Profile
September 13, 2017, 10:55:52 AM
 #2

The more you know about your customers, the more you can provide to them information that is increasingly useful, relevant, and persuasive.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!