NeMA
December 2023
- Trust Relationships: The over-the-counter (OTC) market is decentralized, distinct from conventional exchanges, lacking the oversight of a central authority.If one party to a transaction chooses not to fulfill their obligations, the other party incurs significant losses, leading to a crisis of trust between the trading parties and potentially between the trading parties and their guarantors.
- The traditional over-the-counter (OTC) manual guarantee carries high risks and incurs expensive fees.
- The invitation platform is lacking: There is a lack of a suitable platform for purchasing genuine user invitations.
- KOLs (Key Opinion Leaders) often need to launch lucky draws on platforms to increase exposure, but there is also a credibility issue surrounding these drawings: (1) In the context of Web2, many lucky draws are conducted under the guise of "lucky draws" but are actually advertisements and marketing tactics, exploiting consumers' pockets and potentially extracting their personal information. (2) Platforms manipulate the lucky draw process by making it opaque, allowing them to control the flow of traffic, followers, and the designated winners, raising suspicions of fraudulent behavior. (3) The accounts that win the drawings are not necessarily real humans but bots, leaving genuine users in the dark and uninformed.
The NeMA platform addresses the aforementioned trust crisis through blockchain technology, safeguarding the interests of both users and KOLs (Key Opinion Leaders).
Our project belongs to the Dapp & Smart Contracts track and is a multi-functional integrated OTC trading platform. It is committed to bridging offline transactions in Web3 to the chain, and providing blockchain-based stable guarantee services for buyers and sellers through blockchain technology, to achieve mutual trust, reciprocity and mutual benefit between users and the platform.The main services include c2c+otc mode of OTC support, chain lottery, invitation commission, etc.
The hash lock mode refers to a mechanism in which users guess the original value of the hash value within a specified timeframe to make a payment.It allows users to lock a certain amount of tokens by providing a hash value, and to withdraw them upon satisfaction of specific conditions.When users lock tokens, they are required to provide a hash value, which is associated with specific conditions.When the conditions are met, users can provide the original data matching the hash value to unlock and withdraw the tokens.Simply put, on the basis of smart contracts, both parties first lock assets, and if they input the original value of the correct hash value within a limited time, the transaction can be completed.Under such a mechanism, rapid confirmation of small-value payments, as well as secure transactions and conditional payments, can be achieved, ensuring the credibility and reliability of the transaction.
There are primarily two scenarios:
-
Platform-hosted orders, where users engage in transactions through the matching mechanism of the platform.
-
Users reach a consensus in advance, and the platform merely provides contract support.
Main Process:
-
The user provides information such as the type of digital asset traded, the quantity traded, the price of the transaction, and the duration of the transaction, which is listed on the platform.
Users can also choose from the following options: Trading Methods: Limit Order, Market Order, Stop-Loss Order, Take-Profit Order;Trading Evaluations, etc.
After the user submits the order, it will be publicly displayed on the platform.
-
Another user can search for matching trading orders through the platform.If a suitable order is found, a trading request can be sent.The transaction request should include the following information: the transaction price and the transaction quantity.The user can also choose the transaction method ( limit order or market order).
Note: The prerequisite for successfully sending a transaction request is for the buyer to stake the assets in advance to the smart contract.
-
After the seller confirms, the assets are transferred. Upon receipt of the notification, the seller transfers the assets to the buyer's account, awaiting the buyer's confirmation.
-
Once the buyer confirms the assets have been successfully credited to their account, the smart contract automatically executes the transaction, transferring the digital assets from one party to another, with the transaction information being recorded on the chain.
graph TD
subgraph The user issues a transaction order
Information-Provision(asset type, transaction quantity, transaction price, transaction deadline, transaction method, handling fee)
Platform["Publish to the platform"]
Information-Provision -->|Provide information| Platform
Platform -->|Platform matching service| matchmaking
matchmaking --> Execute-Transaction
end
subgraph Another user matches the order
Search-criteria(search criteria, find suitable orders)
User["send transaction request"]
Search-criteria(Search criteria, find the right order) --> Transaction-request-information(Transaction price, transaction quantity, transaction method, handling fee)
Platform -->|User search criteria| Search-criteria
Platform -->|Find the right order| Transaction-request-information
Transaction-request-information -->|Transaction Request| User
User["Send transaction request"] --> Smart-contract-execution-transaction
end
subgraph Smart contract execution transaction
Platform -->|Automated execution of smart contracts| Execute-Transaction
Execute-Transaction -->|digital asset transfer| Transaction-completed
end
General Process：
-
Release whitelisted transaction orders.
Sellers post whitelisted transaction orders on the platform, typically requiring the provision of the following information: NFT project name, number of whitelisted spots, transaction price (supporting multiple cryptocurrency denomination), transaction method, transaction deadline, and other optional details.
-
Search for whitelisted transaction orders.
Buyers can search for eligible whitelisted transaction orders through the platform.They can filter based on the following criteria: NFT project name, price range, transaction method, and seller reputation.
-
The contract automatically interacts with the front-end, executing asset transfers automatically to safeguard the transaction.
-
After the transaction is completed, buyers can participate in the creation or presale of NFT projects as usual, acquiring the NFT assets.The platform allows both parties to the transaction to evaluate each other, establishing a reputation system for the platform.
**Pol-20 spot trading is similar to the basic process described above, but it is worth mentioning that there is currently no platform that supports pol-20 spot trading. **
The entire process is guaranteed by the platform to ensure secure transactions.Additionally, a friendly reminder is provided:The NFT whitelist trading is an emerging market, presenting certain risks.Before engaging in a transaction, buyers should carefully review the project information and select sellers with a reputable standing.The seller should ensure the authenticity and validity of the provided whitelist quotas.
Award Information: Storing the descriptions and quantities of various awards.
Lottery results: The lottery results, including the winners and prizes, are stored on the blockchain to ensure verifiability and transparency.
Participant Record: The information of the participants (address, participation time, etc.) is recorded on the chain.
Lottery Logic (Contract Details): Implementing the lottery logic in a smart contract to determine the winners.
sequenceDiagram
participant User
participant Smart Contract
User->>Smart Contract: Participate in the lucky draw
Smart Contract->>User: Return to the participation results
activate Smart Contract
Smart Contract->>Prize information: Get award information
Prize information-->>Smart Contract: Return to award information
Smart Contract->>Participants' records: Record participant information
Participants' records-->>Smart Contract: Return the recorded results
Smart Contract->>Lottery logic: Execute the lottery logic
Lottery logic-->>Smart Contract: Return the information of the winner
Smart Contract->>Lottery results: Store the lottery results
deactivate Smart Contract
User->>Smart Contract: Query the lottery results
Smart Contract->>User: Return the lottery results
The core concept of the invitation commission mechanism is first-level commission with permanent binding, providing users with a long-term stable source of income.Specifically, when a user successfully invites a new user to transact on the platform, that user will enjoy the benefits of first-level commission.Meanwhile, this binding relationship will remain permanently valid, ensuring that users can earn the corresponding commission revenue on every transaction made by their subordinates.
In our commission structure, users will receive 1% of the transaction amount of their subordinate users as their direct commission, while the platform enjoys a 3% revenue share from the transaction amount.This advantageous commission ratio not only reflects our recognition of user contributions to enhance user retention but also ensures the continuous operation of the platform with cash flow security.
graph TD
subgraph User and commission mechanism
A[User A] -->|invite| B[User B]
B -->|1% commission| A
B -->|invite| C[User C]
C -->|1% commission| B
end
subgraph Platform
D[Platform] -->|3% rebate on earnings| B
D[Platform] -->|3% rebate on earnings| A
end
UI development is a crucial aspect of the project, directly related to the user experience and the overall usability of the project.
- Requirements Analysis: Clarify the functional and business requirements of the project.Determine the actions that users need to perform on the Web-side, such as registration, login, browsing information, initiating transactions, etc.
- Interface Design: Develop a user interface (UI) design scheme, encompassing page layout, color scheme, and icon usage.With user friendliness in mind, ensure the interface is concise, clear, and easy to navigate.
- Responsive Design: Ensure that the user interface (UI) can be properly displayed and operated on different screen sizes and devices, adopting the principles of responsive design for layout.
- Interaction Design: Design a well-structured interaction flow to ensure users can smoothly complete various operations.This includes form validation, error notifications, and loading status, among others.
- Front-end Interaction with Chain-side: Conduct data interactions with chain-side through APIs or other methods, ensuring that the front-end can retrieve and display data returned by the backend.
- Testing and Optimization: This includes functional testing, performance testing, and compatibility testing.Optimization is conducted based on the test results to ensure the system operates stably.
The development of the on-chain lottery contract is based on the smart contract technology of blockchain, and the following aspects should be considered:
- Lottery Logic: Design the logic of the lottery, including the participation conditions, prize setting, and winning rules.Ensure the logic's fairness and transparency.
- Safety Considerations: To prevent security vulnerabilities in the contract, it is essential to adopt best practices to ensure the contract's safety.This can be achieved by importing third-party libraries.
- Event triggering: Set up events within the contract, allowing users and the front-end to monitor the contract's state changes and promptly update the user interface (UI).
- Randomness Guarantee: Introducing randomness into the lottery process, ensuring that each participant has an equal chance of winning.A random number generation algorithm on the chain can be employed.
- Gas Cost Optimization: Considering the transaction costs, optimize the contract to reduce Gas expenses, enhancing the attractiveness of user participation.
OTC trading contracts must meet the transaction needs of both parties, ensuring security, transparency, and enforceability.The following are the key points for contract drafting:
- Capital Locking Mechanism: The contract is designed to ensure the security of funds for both trading parties, employing a locking and releasing mechanism to prevent fraudulent activities.
- Transaction Parameters: Define the relevant parameters of the transaction, including the transaction quantity, price, and transaction party authentication, among others.
- Transaction Status: Various transaction statuses are defined in the contract to ensure the smooth progress of transactions, including order creation, payment, confirmation, and other states.
- Front-end Integration: Collaborate closely with front-end developers to ensure the front end can properly interact with the contract, implementing the display and handling of transactions.
The primary steps involve:
- Contract Design: Implement Hashlock logic in smart contracts, including asset locking, verifying hash conditions, and unlocking assets.
- Atomicity of Transactions: Ensuring the atomicity of transactions, meaning that prior to the completion of the transaction, the asset is either locked or unlocked, preventing the emergence of intermediate states.
- Contract Security: Consider the security of smart contracts to prevent reentrancy attacks and other potential vulnerabilities.
- Event Notifications: Events are set up within the contract, allowing users and the front-end to monitor changes in the contract's status and promptly update the user interface.
- Testing and Optimization: This includes functional testing, security testing, and more.The contract is optimized based on the test results.
Prepare clear and detailed introductory documents and user manuals.
- UI Development of the primary functionalities.
- The user interface (UI) display on the mobile platform (a demo, primarily used to present the project's logic in advance).
- The contract writing for on-chain lottery.
- Contract drafting supported by OTC trading.
- The open-source technology of hashlock is replicated.
Demo YouTube show:
https://www.youtube.com/watch?v=yNmXrcWoBhc
| function name | 参数 | 返回值类型 | 描述 |
|---|---|---|---|
lock |
_hash: string |
string |
Lock the proposal and return the result string.If the proposal does not exist, has been completed, or has been rolled back, the corresponding error message will be returned. |
unlock |
_hash: string, _secret: string |
string |
Unlock the proposal and return the result string.If the proposal does not exist, is completed, is not locked, or has been rolled back, the corresponding error message will be returned. |
rollback |
_hash: string |
string |
Rollback proposal, return the result string.If the proposal does not exist, is completed, not locked, unlocked, or rolled back, the corresponding error message is returned. |
newProposal |
_hash: string, _role: string, ... |
string |
Create a new proposal and return the resulting string.If the proposal already exists, the time lock is set incorrectly, or the roles do not match, an appropriate error message is returned. |
setNewProposalTxInfo |
_hash: string, _txHash: string, _blockNum: string |
No return | Set the transaction information for the new proposal. |
getNewProposalTxInfo |
_hash: string |
string |
Get the transaction information of the new proposal.If the transaction information does not exist, return "null". |
getNegotiatedData |
_hash: string |
string |
Gets the negotiated data and returns a string containing the initiator and participant information.If the proposal does not exist, an appropriate error message is returned. |
getProposalInfo |
_hash: string |
string |
Gets the details of the proposal and returns a string containing the proposal status and related flags.If the proposal does not exist, it returns "null". |
setSecret |
_hash: string, _secret: string |
string |
Set the key for the proposal and return the result string.If the provided key does not match the hash value, the corresponding error message will be returned. |
getProposalIDs |
无 | string |
Get the hash values of all proposals and return a string containing all the hash values. |
deleteProposalID |
_id: string |
string |
Deletes the proposal with the specified hash value and returns a result string.If the proposal does not exist or the deletion fails, the corresponding error message is returned. |
getIndex |
_hash: string |
(uint256, uint256) |
Get the index and depth of the proposal in the queue. |
setCounterpartyLockState |
_hash: string |
No return | Set the lock status of the other party. |
setCounterpartyUnlockState |
_hash: string |
No return | Set the unlock status of the other party. |
setCounterpartyRollbackState |
_hash: string |
No return | Set the rollback status of the other party. |
The src folder contains test cases for contract functions, and some local tests have been conducted usingtruffle test in the early stages.
| Name | Role | GitHub ID | Wechat ID |
|---|---|---|---|
| TK | pm, Business Logic Developer | Richard tsang202 | tk_nom |
| S7iter | rear-end | S7iter | shihuobiu |
| 探姬 | Full Stack Developer | ProbiusOfficial | ProbiusProtoss |
| V1cent | front-end, UI Designer | L011apa100za | SWS18312967544 |