Home
WowoK Protocol is an AI-oriented web3 collaboration protocol, empowering you to create, collaborate, and transact on your own terms. The WowoK protocol empowers the innovation of super-individuals and creates infinite demand and supply by forming real data and trajectories on the chain. It offers entities lego-like combinatorial collaboration capabilities, supporting a variety of custom transactional and business models, based on the high throughput and low-cost advantages of the Sui blockchain.
*Entity: It could represent the addresses of a super individual or an AI.
WowoK Protocol supports innovation, new business models and services. A series of creations can be undertaken:
- Personalized demand expressions and conditional incentives (Demand & Reward).
- One-click supply publishing, customizing immutable commitment: service progress and transaction terms (Service)
- Realizing transactions at all expected points by verifying existing and future data on the chain(Guard).
- More importantly, it allows for combination and innovation based on all services provided.
WowoK Protocol empowers super individuals to achieve their desires: collaboration between super individuals and AI.
- Data on open chain databases can be defined by super individuals. This data can then be referenced cross-organizationally, and resources of collaborative entities can be shared, ultimately reducing collaboration friction (Repository).
- Creating service progress that meet consumer market needs, controlling collaboration pace and quality, achieving sustainable supply satisfaction (Machine).
- Suppliers are able to integrate their services with those of other suppliers to form an interconnected service network that can adapt to various customer needs through dynamic linking mechanisms.（Service）
- The completion of one Progress can trigger the start of another Progress. This connection mechanism supports cross-organizational and cross-service collaboration, allowing different suppliers and service providers to work together to meet the comprehensive needs of customers.（Progress）
- Treasury supports the management and allocation of funds in complex collaborative processes, providing the necessary flexibility to adapt to changing business needs.（Treasury）
- WowoK Protocol targets AI-tagged data that AI can efficiently recognize, enabling efficient matching of personalized demands.
- Private ownership: Data ownership and privacy protection are essential requirements in the digital age. In the Wowok Protocol, data is authentic and owned by entities.
- Shared ownership: Permission Creator manages the granular permissions of entities (address) and objects, enabling ownership management and managed collaboration (Permission).
- Privacy-preserving: Private data can be securely transmitted using address-level encryption, which provides peer-to-peer sharing capabilities. This method ensures that on-chain privacy is maintained, safeguarding sensitive information such as contact details and delivery addresses (Posting & Order info).
Object is the fundamental unit of the Sui blockchain, featuring:
- UID: Each object has a unique identifier (UID) that can be searched for on the blockchain as an address.
- Ownership: Address-owned objects are accessible only to their owners; immutable objects have no owner and are usable but not mutable, transferable, or deletable by anyone; shared objects are accessible to all, with ownership governed by protocol rules.
The WowoK Protocol implements complex permission controls, with each object having a Permission table or Permissions. Permission implements access and operation control of specific objects by assigning permission indexes to entity addresses. The creator of permissions can transfer permissions of permission objects, and the administrator is responsible for assigning permissions, which simplifies the permission assignment and audit process. Fine-grained permission control reduces the risk of unauthorized access and enhances the overall security of the system.
The WowoK Protocol provides the following infrastructure:
- Contract objects: Transaction models including service & order, demand, and reward objects primarily implement collaborative supply and demand expression and timely incentives, combining protocol objects flexibly into a complete service set.
- Progress objects: The WowoK Protocol uses state machines to clearly represent process diagrams, making collaboration processes visible and controllable. Machines are static state machines showing all possible states of a process; progress is the instance of machine, showing the actual states during the progress' execution.
- Common objects: In the WowoK Protocol, common objects like guards, permissions, repositories, and votes facilitate collaborative condition validation, permission control, data storage, and voting decisions.
These three types of infrastructure enable better combination and innovation, allowing both supply and demand parties to achieve effective transaction consensus and secure trading.
Web3 provides a decentralized and distributed network environment that emphasizes users' control over their own data, while AI improves the speed and quality of decision-making, optimizes user experience, and plays a huge role in data processing and analysis by learning and imitating human intelligence. As an example of the combination of Web3 and AI, the WowoK protocol provides data, scenarios, and interaction rules for AI and individuals. Under this framework, AI can generate new and real data in Web3 according to these rules and change the data through interaction. AI uses its computing power to make decisions that are beneficial to entities, achieving:
- More effective supply and demand publication and matchmaking, reaching transaction outcomes.
- Prediction and optimization: Based on existing supply and demand and its capabilities, AI can create more personalized or scaled supply and demand.
- Universal uniqueness: Blockchain addresses are globally unique, unrestricted by any platform or organization, unifying all resources and data.
- Identity and reputation: Addresses can be used to build decentralized identity systems, storing identity information, history, and achievements.
- Data ownership: Addresses are controlled by private keys, with the private key holder having ownership and operational rights over the address. Users can fully control their data and assets without relying on any third-party platform.
Demand refers to the personalized requirements that users can express in any form. Through AI-driven data matching, the most satisfactory services can be identified to make these demands easier to fulfill. It is an incentive mechanism, a demand-centric transaction matching model powered by AI-driven search to facilitate deals.
| Attribute | Definition |
|---|---|
| Description | Describe your personalized need |
| Bounty | Token or any transferable asset as a reward for a satisfactory presenter; if no satisfactory presenter is picked, the Entity with permissions can reclaim the bounty after the deadline. Bounty can be increased but not decreased. |
| Duration | The start time is based on the timestamp of the successful on-chain transaction. Deadline can be extended but not shortened. Bounty can be reclaimed after exceeding the deadline. |
| Guard | Address that meets the guard conditions and submits a service |
| Presentation | Service presenter provides the service and the recommendation to the service |
| Refund | Bounty Remained would be Refunded while time over |
Traditional travel planning projects involve multiple communications and comparisons, which is time-consuming and labor-intensive. By publishing requirements, travelers can put forward all their requirements at once, which greatly improves efficiency. The interaction between travelers and service providers becomes more direct and efficient, while providing a more fair and transparent trading environment for both parties.
Traveler's needs launch:
Tom wanted to experience the Great Migration in Africa and was looking for a relaxing safari with accommodation close to nature and a guide who could provide knowledge of the wildlife and natural environment.
Response from the platform:
- AI can optimize service processes and reduce unsatisfactory experiences by analyzing the return rate and user feedback of services. For example, if the return rate of this travel service has reached 30% since its launch, AI can automatically adjust the recommendation algorithm to reduce the frequency of recommendation of this service.
- Fun and participation: Web3 technology supports the creation of decentralized travel communities where travelers can share experiences, evaluate services and participate in the decision-making process. Response from service providers:
- Platform AI identifies and responds to travelers' personalized needs and provides customized travel suggestions by analyzing a large amount of user data.
- Service providers develop new services that meet the needs.
- Provide transparent service progress to ensure travelers' trust.
- Through the reward mechanism, users can be encouraged to participate in the evaluation. For example, AI can adjust the service content based on real-time feedback from users to provide an experience that better meets user expectations.
Services are tradeable supplies with the following features:
- Ability to integrate trusted on-chain services to create personalized services.
- Service presenters can define, publish, and manage services flexibly, including details like service descriptions, product lists (with prices and stock), payees, withdrawal and refund rules, breach reward and custom interactive endpoints.And manage collaborators more effectively by decomposing permissions.
- They offer engaging transaction models and consensus preferred by market participants, such as financial and procedural agreements, and incorporate automated systems to customize service processes for smooth and transparent collaboration.
| Attribute | Definition |
|---|---|
| Token | All items within the service will only accept this token |
| Payee | Payee for the order |
| Description | Introduction |
| Item detail | Item name, price and stock of items for sale |
| Withdraw guard | Payee's withdrawal agreement, allowing for percentage-based withdrawals under certain guard conditions |
| Refund guard | Payer's refund agreement, specifying the percentage to be refunded based on guard conditions |
| Breach reward | Compensating buyers for non-performance or under certain conditions |
| Endpoint | Customizable interactive interface |
| Repository | Storage of service-related data |
| Machine | Consensus on service progress |
| Buy guard | Service purchase accessible only to users meeting buyer's guard conditions |
| Required information | Buyer information, such as contact details and shipping address, will be encrypted |
| Allow ordering | A commitment to buyers regarding the immutability of machines, withdrawal, and refund guards, token. Services can also be temporarily suspended or restarted based on service conditions |
| Clone service | Duplicating a service and being able to modify transaction token and consensus |
*The service is released and orders are accepted. At the same time, Machine, guard, etc. cannot be changed.
Customized Kenya Wildlife Safari Experience
The Wowok platform detects companies that highly match the needs Tom has outlined and pushes Tom's needs to these companies, which will then detail a tour plan based on Tom's needs.
Service Provider Announcement:
In order to deeply meet the needs of tourists to experience the African Great Migration, Natural Explorer Tours has launched an in-depth tour program for the African Great Migration. The company promises to provide professional guides to lead the tour, luxury tents or eco-lodge accommodations to ensure that you don't miss any of the best moments to see the Great Migration.
Tom suddenly received an emergency call from home and needed to return immediately to deal with family affairs, which meant that he could not continue the original safari itinerary. Faced with this emergency, Tom needed to cancel the remaining itinerary and hoped to get a corresponding refund.
Details:
- Traditional travel agencies have fixed itineraries, lack flexibility, and are difficult to adapt to the temporary changes in travelers' needs.
- Because it is difficult to make adjustments or cancellations, Tom is not only worried about the situation at home, but also faces possible financial losses.
Solution:
- Tom can submit an emergency cancellation request through the Wowok platform and provide proof of the emergency.
- The Wowok platform will automatically verify whether Tom's emergency guard conditions meet the refund policy.
- Tom meets the emergency guard terms and will refund the part of the service he enjoyed in his paid units according to the agreed proportion.
- The accommodation provider returns the unused accommodation funds to the tour company.
Order represents the transaction conducted between a seller and a buyer, containing detailed records of the purchase, including product details, quantity, price, discounts, etc. Once the buyer successfully makes the payment, an order is generated, and refunds and withdrawals are processed through a consensus mechanism. Protecting buyer privacy: When storing additional information required by the buyer, encryption is used to protect user privacy.
| Attribute | Definition |
|---|---|
| Detail | Item name, price, quantity, to pay |
| Required info | Request buyer information |
| Discount | Discount used at the time of payment (Maximum discount is selected by default) |
| Progress | Service progress of the order |
| Payer | Payer's address for the order |
| Payed | Amount paid by the payer |
| Withdraw guard* | Payee's withdrawal agreement, allowing for percentage-based withdrawals under certain guard conditions |
| Refund guard* | Payer's refund agreement, specifying the percentage to be refunded based on guard conditions |
| Breach Reward | Compensating buyers for non-performance or under certain conditions |
*Withdraw guard & Refund guard: If one party withdraws a specified percentage of the funds, the other party can claim the remaining percentage. For example, if the Order Payer takes 80% of the refund, the Payee can retrieve the remaining 20% of the funds.
Traveler's Needs Met:
- The traveler chose the services provided by Nature Explorers Travel Company after comparing multiple travel services.
- The original price was $5,000 USDT, and the early bird customer enjoyed a 10% discount, ultimately paying $4,500 USDT.
- Real-time order progress tracking, from trip preparation to departure, to participating in various activities, everything is under control.
Service Provider's Promise:
Nature Explorers Travel Company guarantees that its services meet the traveler's expectations and provides necessary safeguards.
- Fulfillment of service commitment: Before Tom's trip, he paid the full amount. If Nature Explorers cancels the service before Tom's departure, the Withdrawal and Refund Protection Guard will ensure that Tom can get back the full amount he paid.
- Rights protection: Tom found that his accommodation conditions did not match the luxury tents promised in the contract, and were actually provided with ordinary tents. The breach compensation Guard was activated, and the smart contract automatically calculated the compensation amount based on the breach of contract and compensated Tom with an additional 5% of the cost as compensation.
- Response to unforeseen circumstances: During the trip, Tom suddenly fell ill and needed to return home immediately. He applied for a refund through the emergency guard. The emergency guard evaluated the situation based on Tom's medical certificate and the emergency clause in the contract, and executed a full refund after confirmation.
Service admin (defined by Service Permission) can set the discount for service(s). After the discount is launched, it becomes an asset for entites that cannot be tampered with.
| Attribute | Definition |
|---|---|
| Name | Discount name |
| Discount type | - Percentage discount - Fixed discount |
| Minimum amount | A discount will be valid if the purchase price is greater than or equal to the minimum amount required |
| Quantity of dicount object to dispatch | The number of discounts each recipient has. |
| Period | Valid during the start and end times |
| Service | For services or a service |
- Send to Existing buyers: Service administrators (Defined by Service Permission ) can send discounts to eligible buyers by setting guard, such as offering a 20% discount to buyers with multiple service engagements.）
- Reward for Future buyers: Discount can be a bonus transferable asset, claimable as a reward upon meeting certain conditions. Buyers can earn discounts of varying degrees by completing different levels of guard tasks:
| Condition | Guard | Discount percentage |
|---|---|---|
| Complete 1 task | Sense 1: Invite a new address to use the service Or Sense 2: Share the service with two addresses |
90% discount |
| Complete 2 tasks | Sense 1: Invite a new address to use the service And Sense 2: Share the service with two addresses |
80% discount |
Tom is an adventurer who loves to travel. He has participated in two Kenya safari trips and one Tanzania mountaineering trip through Nature Explorer Travel. As a loyal customer, Tom meets the conditions for Nature Explorer Travel's newly released exclusive loyal customer discount.
Tom's travel records are stored in the database of Nature Explorer Travel, and his participation records are updated after each trip. Therefore, when Tom logs into the platform, the system verifies the number of trips Tom has participated in through guard.
The loyal customer discount requires at least 3 trips with its travel agency. Tom just meets the conditions and can enjoy a 15% loyal customer discount, which is an additional benefit to the early bird discount.
Throughout the trip, travelers can view the service progress in real time and understand the conditions for refunds and compensation.
Through this case, travelers can not only enjoy our special discounts, but also experience a transparent and convenient payment and refund process to ensure that their travel experience is both economical and worry-free.
- Businesses can customize transaction modes and rules, breaking free from the constraints of web2 platform rules. For example:
-
Setting custom transaction modes.
- Refund guard: Buyer get different refund ratios based on the refund time.
- Withdraw guard: Service provider can withdraw funds when the progress node's status is Transaction successful.
-
Reference objects on the chain, leveraging existing and comprehensive repositories, guards, and machines on the chain to create super high-quality services.
-
Defining own service machines, creating a new service by combining multiple suppliers.
Agent combines services that meet the traveler's needs into a new service:
- Buyers can witness the complete set of entitlements and service progress, including conditions for refunds and compensation. Service Buyers can view the full terms of service, payment agreements, and service progress:
- Users' service behaviors can be trained into their own consumption habits AI. With user consent and privacy protection, the blockchain can match the most satisfactory and needed services.
Machine embodies the entity of the business. The machine defines the various states, operations, permissions, and delivery standards in the business, and generates progress instances for different customers.
Machine represents a boundaryless collaboration that defines core data, sets its own consensus, and establishes collaborative patterns. Different entities, based on an unbreakable consensus, can cross organizational boundaries to achieve collaboration around service.
Within Machine, collaboration data can be aggregated and analyzed to identify issues in the collaborative process, forming authentic data and enhancing collaboration efficiency.
Machine connects to trusted tools, consensus, shared repository, and completes progress. It represents a state diagram, consensus repository, and permission for machine management.
A Machine State Diagram in the WowoK Protocol is a service progress diagram that includes operators and nodes.
Operators: These are entities that execute operations and can be either order payer (buyer) or collaborators involved in completing a service. There are two types of operators:
- Permission indexes: These are entity addresses with specific Permission Indexes assigned by Permission.
- Progress Operators: The Machine builder inputs a progress operator name, which can be a protocol-provided name like "Order payer" or a custom name like "Delivery person", different entities at different progress stages. Assuming the progress operator is Order payer, the progress is initiated after the buyer makes the payment.
Nodes: Nodes represent states that can be reached by satisfying guard conditions. A pair of adjacent nodes is called a node pair, which can have one or more operators. By default, if one operator meets the guard condition, the progress can move to the next node. A threshold can be set for collaborative tasks requiring multiple operators.
Weight & Threshold: The threshold is a total value, defaulting to 100. When the sum of the weights reaches the threshold, the next node is triggered. For example:
- If two operators have weights of 50 each, both must satisfy the guard to proceed.
- If three operators have weights of 50 each, any two can satisfy the guard to proceed.
Guard: The conditions that an operator must meet to complete an operation.
Machine State:
- Pause running a progress: Cannot run a progress.
- Allow running a progress: Can run a progress. Once a progress is initiated, it indicates that a consensus has been reached, and the Machine cannot be modified. To edit the Machine, a clone can be made and then edited.
Endpoint: the Machine Permission Admin can customize an interface to provide a better user experience. Users can perform operations at corresponding consoles based on their current node.
-
Repository: Machines are assigned a repository where all progress data are saved. The Repository is used to define data and create new collaborative models.
-
Permission: Adding Permission to the machine allows for the separation of process operations and entity management.
In the carefully planned Kenya safari trip by Nature Explorer Travel Company, we use machines to create a smooth and efficient travel service network with the concept of borderless collaboration. Here is how we use this technology to bring tourists an unforgettable adventure experience:
After Tom places an order, a personalized travel progress instance will be generated for Tom, customized according to his choices and needs.
Set up a machine state diagram, including key nodes, such as order confirmation, trip start, activity participation, trip end, etc.
Each node represents the completion of a travel stage, and the guard condition ensures that each stage is executed as expected. For example, if Tom does not confirm the order within 24 hours, the order will be automatically canceled.
After Tom confirms the order, the progress begins to be executed to ensure that the service is delivered on time. If Tom needs to return due to physical illness during the journey, Tom needs to upload the certification information provided by the recognized relevant agency to the chain. Then the emergency guard will verify whether the certification can be trusted based on the certification information. If it can be trusted, a certain percentage of the refund will be given according to the content of the unfulfilled itinerary.
Progress is an instance of running machine, including the original machine, parent progress, repository, current and historical nodes, and operators.
| Attribute | Definition |
|---|---|
| Current node | Current state |
| Current operator | Address that completes the current operation |
| Historical node | Historical progress state |
| Historical operator | Historical operation and operator |
| Original machine | Complete progress, predicte workflow trajectory |
| Parent progress | Independent progress of collaborators |
| Repository | Store the data generated by the collaboration entity during the runtime of Progress |
Entities can directly view the progress and state, providing a reference for the next collaborative combination. Collaborators receive operation notifications and can perform operations on the corresponding page, accumulating their completed progress as a form of capability proof.
Progress Initiator, two ways to start a progress:
- Based on the allocation of Machine Permission, the entity with the granted permissions can initiate progress, set a progress operator, and manage repositories, among other capabilities.
- Service Progress Initiation: After a certain address pays for a service and forms an order, it automatically becomes the order payer for the progress and initiates the progress.
Parent progress: Each business has its own progress, and collaboration between businesses can be achieved through progress connections. For example, in a product transaction progress, it is a parent progress of the shipping company's progress.
Repository: The shared database for collaborators. All service or progress collaboration consensus can be stored, managed, and written in the progress repository.
A progress is a running instance of a machine in our company's travel service. It contains the complete progress track of the original machine, the independent progress of the parent progress, and the cooperation data generated in the repository.
After Tom signs up, his progress instance uses a shared repository to record all relevant travel data, such as accommodation reservations, tour guide arrangements, activity participation, etc. Operators include Tom (as the order payer), travel agency (as service provider), tour guide, and accommodation provider.
The travel agency, as a service provider, coordinates the tour guide and accommodation provider based on the information in Tom's progress instance to ensure that all services are delivered on time.
Tom can view his travel progress in real time, including upcoming activities, accommodation arrangements, and transportation arrangements.
Through progress management, Tom's travel service network becomes smooth and efficient, ensuring that every detail is perfect.
Guard refers to a mechanism used in blockchain to ensure data integrity and security. Guard can monitor and evaluate on-chain data in real time to ensure data security and integrity; it supports cross-platform and cross-system data processing and is not restricted by a single system or platform. Guard has guard conditions, which are preset conditions. Verification can only pass when these conditions are met, otherwise verification fails. Guard conditions can be specific attributes of data, such as timestamps, source verification, logical combinations, etc. For example, users must have a good reputation and an account balance of more than 100 USTD to enjoy free room upgrades. After Guard is started, it will become an immutable object, and all data generated by the object can be referenced by Guard. By referencing the Guard address, it can be used in scenarios that require conditional verification, such as receiving rewards, refund conditions, voting qualifications, etc.
| Attribute | Definition |
|---|---|
| Description | Introduction |
| Sense | Senses determine conclusions of true or false, and can be combined using 'and' or 'or' - Combining senses with 'and' requires all conditions to be met for validation - Combining senses with 'or' allows validation if any condition is met |
| Constant | Frequently used data or future data source |
-
Reward Guard: If someone sets me (0x538d06) to admin of Hogwarts Permission (0x64f34d), they can claim a reward of 50 USTD.
- Guard: Verify whether the address 0x538d06 is an Admin of 0x64f34d [Hogwarts Permission].
-
Refund Condition: Return within 7 days for a full refund; return within 15 days for an 80% refund
-
Sense 1: Order Time of 0x64f34d [Trip Service]<7 days, 100% refund
Or
-
Sense 2: Order Time of 0x64f34d [Trip Service]<15 days, 80% refund
-
-
The guard can reference future data, such as orders generated by services in the future or progress initiated by machines in the future.
For a Kenya safari trip:
Guard can ensure that each stage of the travel service meets the predetermined standards and conditions, thereby protecting the customer's data and travel experience.
-
Trip Start Guard:
-
Scene: Tom's travel itinerary should start on the specified date.
-
Guard function: If the trip fails to start at the scheduled time, the Trip Start
-
Guard will notify Tom and provide the option to reschedule or cancel the trip.
-
Refund Guard:
-
Scene: Tom is not satisfied with the service.
-
Guard function: If Tom is not satisfied with the service, he can apply for a certain percentage of refund or change the service plan
-
-
Emergency Guard:
-
Scene: Tom encounters health problems during the trip.
-
Guard function: Emergency Guard allows Tom to contact the travel support team immediately and provide medical assistance or itinerary adjustments according to the situation.
-
-
Loyalty Customer Guard:
-
Scene: Since Tom is a loyal customer, he hopes to get additional discounts exclusive to loyal customers in addition to the early bird discount.
-
Guard function: Loyalty Customer Guard verifies Tom's travel history and participation times to confirm that he meets the criteria of a loyal customer. If Tom meets the requirements, he will receive an additional 5% loyalty discount.
-
Through these Guard settings, Nature Exploration Travel can ensure that every aspect of the itinerary is managed effectively, while protecting the interests of travelers and improving the satisfaction and safety of the travel experience.
Permissions are the allocation of operating rights to objects. Each object creation requires the assignment of a permission. One permission can manage multiple objects. By assigning permission indexes to entity addresses, fine-grained access control can be achieved, and one-stop management of personnel permissions can also be achieved. Permission management allows one-stop management of personnel permissions, simplifying the permission allocation and audit process.
| Attribute | Definition |
|---|---|
| Description | Introduction |
| Builder | Creator and admin for Permission : - Creator: Transfer the authority of the Permission object; manages admins - Admin: Distribute permissions |
| Permission table | Manage permission indexes for entity addresses |
The diagram below shows the Permission table of the Repository, where this Permission can manage multiple Repositories.
The company has a repository for Kenya trips, which contains all relevant information about Kenya safari trips, including itineraries, customer information, payment records, etc. The permissions will be assigned as follows:
- Trip planning permissions:
- Entity address: 0x123abc
- Permission index: Trip planner, who can view and edit Tom's personalized itinerary.
- Function: Allows the trip planner to customize the trip route and activities according to Tom's preferences and needs.
- Financial processing permissions:
- Entity address: 0x456def
- Permission index: Finance personnel, who can process Tom's payments and possible refunds.
- Function: Ensure that Tom's payments are processed correctly and that refunds can be performed quickly if necessary.
- Customer service permissions:
- Entity address: 0x789ghi
- Permission index: Customer service representative, who can view Tom's travel information and provide real-time consultation and support.
- Function: Enable the customer service team to respond to any questions or problems of Tom in a timely manner and provide necessary assistance.
Permission application during the trip:
-
Itinerary confirmation: Tom uses his customer service permissions to log in to the platform, view the detailed itinerary, and confirm all arrangements before departure.
-
Emergency handling: During the trip, Tom encountered an emergency, and he used the customer service permissions to quickly contact the emergency response team to obtain the necessary support.
-
Feedback submission: After the trip, Tom logs in to the platform again using his permission index to submit his feedback and evaluation of the travel service.
Through such a permission management mechanism, Nature Exploration Travel Agency can ensure the security and efficiency of its business processes while complying with data protection regulations and protecting sensitive information of customers and companies.
Repository serves as a consensus and shared data library, enabling the definition, management, and collaboration on data.
Policy Name is the title for data indexing, and enables the implementation of data consensus. In different modes, only entity addresses with the Permission index are allowed to submit data for the designated Policy Name.
Entities on the blockchain can reference repositories with established consensus, facilitating infinite combinations of data.
| Attribute | Definition |
|---|---|
| Description | Introduction |
| Value type | Bool, string, number... |
| Policy | Data rules: Who can write, data name, data type |
| Policy mode | -Free mode: Allows entry of data other than policy. Used for informal, non-consensus situations. -Strict mode: Prohibits entry of data beyond policy. Used in formal, fully consensus contexts. |
| Data | Stored data |
| Repository type | 1. General Repository: Created by entity 2. Wowok Grantee Repository: Created by the Wowok protocol |
In order to improve the service quality of Kenya tours, Nature Exploration Travel Agency decided to use the repository to collect and manage traveler feedback and optimize itinerary arrangements.
- Define data consensus:
-
Strategy name: Kenya trip experience feedback
-
Strategy description: Collect and analyze traveler satisfaction and recommendations
-
Permission index: 0xFeedbackPolicy
-
Only entities with appropriate permissions to index can submit or modify data related to the Kenya Tour experience.
- Data management:
-
The repository will contain travelers’ ratings, reviews, recommendations, and service provider responses.
-
For example, if Tom is not satisfied with the tour guide service, he can submit feedback through his permissions and the feedback will be stored in the repository for all relevant parties to access.
- Grantor and transferee:
-
Nature Discovery Tours can become a grantee, recognizing as a grantee an individual or team that has made a significant contribution to enhancing the experience of traveling to Kenya.
-
For example, if a tour guide receives high ratings from travelers for his excellent service many times in a row, Nature Quest Tours can award him with the title of "Outstanding Tour Guide", which will be recorded in the repository.
Treasury can be defined as a system for managing assets and recording financial transactions. The treasury not only tracks the inflow and outflow of assets within an organization, but also records all transaction histories to ensure the transparency and auditability of financial activities.
| Attribute | Definition |
|---|---|
| id | Unique identifier of the financial library |
| Description | Description of the financial library |
| balance | Balance of the financial library, which may contain multiple currency types |
| history | Detailed history of all transactions in the financial library |
| deposit_guard | Guard address that controls who can deposit funds into the financial library |
| withdraw_guard | Guard information that controls withdrawal permissions, including addresses and corresponding withdrawal conditions |
| withdraw_mode | Mode or rule for withdrawal |
| inflow | Total income of the financial library |
| outflow | Total expenditure of the financial library |
| permission | Address with permission to operate the financial library |
- Internal Model
Nature Explorer Travel wants to reward its outstanding employees.
- The company's finance department allocates a bonus to the tour guide who won the annual best service award through the treasury system.
- The bonus is not issued in a specific amount, but is determined based on the employee's performance and company policy.
- Under this model, there is a greater risk because there is a lack of specific control over the outflow of funds, which may be abused or misallocated.
- External Model
During the Kenyan wildlife trip, as a satisfied and generous traveler, Tom decided to use the treasury to issue rewards to fellow travelers in recognition of their positive contributions and friendly interactions during the trip.
- Tom transferred a sum of money to the treasury for reward distribution.
- Tom determines the distribution weight of the reward based on the performance and contribution of the traveler during the trip.
- Travelers can withdraw according to the Guard conditions, and it is recorded in the history of the treasury.
- All reward issuance and treasury operations are recorded on the blockchain, ensuring transparency and auditability.
For example, Tom decided to issue a special reward to Alice, a traveler who helped him find a rare bird observation point during the trip. He sets the reward conditions through the vault system and adds Alice's address to the withdrawal whitelist. Once the conditions are met, the corresponding amount is automatically transferred from the vault to Alice.
- Withdrawals can be made both internally and externally
In order to ensure the quality of service, Nature Explorer Travel requires service providers, such as tour guides, hotels, etc., to deposit a certain amount of money in the vault as a deposit.
- The service provider deposits the deposit before the service begins
- When the traveler is satisfied with the service, the deposit can be released to the service provider through the Guard condition.
- If the service does not meet the standards, part of the deposit may be used as compensation.
- This model establishes a trust mechanism between service providers and travelers, ensuring service quality while protecting the interests of travelers.
In these cases, the vault system provides a flexible and auditable financial management platform that ensures the transparency and compliance of fund flows. Through smart contracts and Guard conditions, the vault can automatically perform fund deposit and withdrawal operations, reducing the risk of human error and fraud.
Order arbitration is a mechanism for resolving disputes or conflicts that may arise between the parties during the order fulfillment process. Order arbitration is performed by a third-party arbitrator, such as a court, to evaluate the disputed points and make a fair judgment.
| Attribute | Definition |
|---|---|
| id | A unique identifier used to distinguish between different arbitration cases. |
| description | Description of the arbitrator. |
| voting_guard | Voting guard is a map, the key is the address, the value is the voting weight. If it is empty, it means everyone can vote. |
| usage_guard | Use guards, optionally, to control who can call this arbitration. |
| fee | Costs associated with the arbitrator. |
| endpoint | An endpoint is a URL address used for further interaction or information. |
| bPublished | Indicates whether arbitration has been published. |
| permission | A list of permissions that controls who can perform actions on arbitration cases. |
Tom ordered a souvenir from his trip to Kenya online through Nature Explorer Travel. However, after the expected delivery date, Tom did not receive the item. He decided to resolve the issue through the order arbitration system.
- Tom filed an arbitration request on the order page, stating that he did not receive the ordered souvenir.
- The merchant and the courier responsible for the delivery submitted their evidence, including the shipping record and the courier receipt certificate, to prove that they had completed the delivery as required by the order.
- According to the platform rules, a jury is randomly selected or jointly appointed by Tom and the merchant, who will serve as a third-party arbitrator.
- The jury members review the evidence provided by Tom and the merchant and vote. All data generated during the voting process is visible to all parties involved.
- The jury makes a decision based on the majority vote. If the decision is in favor of Tom, the merchant needs to compensate or re-deliver the item according to the platform rules.
The object Wowok Grantor is owned by Wowok Protocol. Any entity can apply to become a grantor to the Wowok protocol. The grantor acts as a trust transfer tool and can authenticate other entities as grantees. WowoK protocol generates a grantee repository for authorized grantors, which is used to manage and store grantee information.