Web3-Based Functional-Unit Software Contract-Linked Utility Token System and Method for Operating the Same
The Genie Token system addresses FP-based reward calculation and real-time payment challenges, enhancing transparency and user participation by integrating with Web3 platforms for efficient software development project compensation.
Patent Information
- Application Number
- KR1020250217028
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2025-12-31
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2045-12-31
AI Technical Summary
Existing software development project compensation systems lack clarity in reward calculation based on Function Points (FP), lack transparent compensation linked to development progress, hinder real-time payment and asset conversion, and lack an integrated utility token ecosystem for various real-world usage scenarios.
A Genie Token system that calculates rewards based on FP, enables real-time automatic payments and asset conversion through smart contracts, and integrates with Web3-based shopping malls for transparent and efficient token usage.
The system provides clear compensation criteria, reduces global remittance and currency exchange risks, enhances transparency, and encourages user participation through real-world token usage.
Smart Images

Figure 112025149750894-PAT00002_ABST
Abstract
Description
Technology Field
[0001] The present invention relates to a Web3-based utility token system linked to functional unit software contracts and a method for operating the same. More specifically, it relates to an integrated payment operating system and a method capable of issuing utility tokens linked to functional unit contracts and milestone management in Function Point (FP)-based software development projects, automated reward distribution, real-time exchange, and settlement of real assets. Background Technology
[0002] Traditionally, in software development projects, developer compensation is often settled on a lump-sum basis. Consequently, payment is delayed in the event of project delays, and in global transactions with overseas developers, various risks and costs arise, such as currency exchange fees, payment failures, and exchange rate fluctuations, making it difficult to establish an efficient compensation system. Furthermore, in existing contract structures, quantitative contract standards based on functional units are unclear, leading to a lack of objectivity and transparency in compensation calculation. This, in turn, increases the potential for disputes between project clients and suppliers.
[0003] Recently, blockchain-based smart contract-based automated payment technology is being researched as a solution to these problems. By utilizing smart contracts, rewards can be automatically paid when development scopes and conditions are met, transaction and payment history can be recorded immutably, and real-time payments can be implemented anywhere in the world using universal Web3 tokens. However, the current situation is inadequate; commercial platforms that integrate contract execution, payment, and history management procedures by linking function-based quantitative analysis results with blockchain-based automated payment systems in real-time have been limited, and related attempts remain at the stage of separate modules or experimental phases. The problem to be solved
[0004] The present invention aims to overcome various existing limitations related to compensation and payment systems for software development projects.
[0005] First, there is a lack of a token reward system capable of clearly calculating reward criteria based on quantitative contract standards derived from Function Points (FP), which leads to a problem where the reward system becomes unclear.
[0006] Second, due to the lack of automated and conditional payment functions for each project stage (milestone), a transparent compensation system linked to development progress is required.
[0007] Third, user convenience and usability are hindered due to the lack of Web3 payment infrastructure that allows rewards to be exchanged for currency or converted into real assets in real time.
[0008] Fourth, we aim to address the lack of an integrated utility token design that encompasses various real-world usage scenarios within the token ecosystem, such as staking, deposit, distribution, and real-world payment.
[0009] The various problems that the present invention aims to solve are not limited to those mentioned above, and other unmentioned problems will be clearly understood by those skilled in the art from the description below. means of solving the problem
[0010] The present invention relates to the structural and technical design of a Genie Token system in order to effectively solve the above-mentioned problems.
[0011] First, a Function Point (FP)-based contract module is introduced to the platform to enable Genie tokens to be automatically calculated and allocated according to each functional contract unit.
[0012] Whenever there is a state change, such as in the project schedule, milestones, or inspections, the smart contract automatically verifies these conditions in real time, and if the conditions are met, the reward is executed immediately.
[0013] In addition, Genie tokens are linked with PG (payment gateway) and decentralized exchanges (DEX), allowing them to be swapped for other digital assets in real time or used for external payments, and these swap and exchange structures are also supported in stages through smart contracts.
[0014] Furthermore, by enabling the purchase of actual products with Genie Tokens through integration with Web3-based shopping malls and implementing an integrated utility token ecosystem that encompasses physical payments, the system is designed to ensure that all linked functions—including various rewards, payments, currency exchange, and physical purchases—operate automatically, in real-time, and transparently.
[0015] In addition, the token operating device includes a verification module that determines the consistency of a user's payment or transaction request and whether payment conditions are met; and a token storage module that controls the storage of contract-based issued tokens in a locked state until conditions are met, and transfers them to the user's wallet when conditions are met.
[0016] Additionally, the token operating device includes a staking module that performs an internal token approval procedure after validating a user's staking request through a verification module, deposits the token into an external staking pool, issues proof tokens regarding the staking stake, returns the principal through unstaking upon early termination, and performs token unlocking and reward distribution upon expiration of the staking period to pay the principal and reward tokens to the user's wallet.
[0018] Specific details of other embodiments are included in the detailed description. Effects of the invention
[0019] According to the present invention, by introducing a quantitative contract structure based on function points, compensation criteria are clearly calculated, and the efficiency and reliability of the contract can be significantly increased through automatic payment by smart contracts.
[0020] In addition, the ability to provide global real-time rewards through Genie Tokens significantly reduces the costs and time risks associated with overseas remittances and currency exchanges.
[0021] Furthermore, by providing an environment where Genie Tokens can be practically used through integration with Web3 shopping malls or affiliate services outside the platform, the real-world value of the token can be increased and participation in the ecosystem can be activated.
[0022] Payment history, distribution records, and usage history are all transparently recorded and automatically verified on the blockchain, thereby dramatically improving the reliability and transparency of the entire system.
[0023] Finally, using Genie Tokens within the platform provides various benefits, encouraging voluntary participation and cooperation among users and enabling the formation of a sustainable reward ecosystem.
[0024] It will be fully understood that various embodiments of the technical concept of the present invention may provide various effects not specifically mentioned. Brief explanation of the drawing
[0025] The drawings of the present invention illustrate the main procedures and functional flows of each module and system. Figure 1 shows the internal structure of the token module responsible for core roles such as token issuance, verification, and payment, and the inter-component relationships of each component. Figure 2 illustrates the step-by-step flow of token issuance after a functional unit contract is concluded, and the subsequent deposit, unlocking, and transfer to user wallets of the tokens depending on whether milestones and conditions are met. Figure 3 illustrates the entire process, from automatically generating proof data upon achieving project milestones based on a smart contract to unlocking tokens and processing reward distribution or refunds. Figure 4 illustrates the flow of the swap procedure, including request verification, internal approval, integration with an external DEX, and reflection of results, when a user requests a swap of reward tokens. Figure 5 illustrates a series of staking processes from a user's token staking request to condition verification, staking pool deposit, issuance of proof-of-stake tokens, termination, and return of principal and rewards. Figure 6 illustrates the overall flow of the physical payment processing procedure, from asset classification, information verification, payment processing, system status update, and notification transmission after payment is completed, when a user requests the purchase of physical assets or off-chain rights (e.g., licenses / rights, etc.) such as software / service usage rights. Specific details for implementing the invention
[0026] Throughout the entire invention, the same reference numerals refer to the same components. The invention does not describe all elements of the embodiments, and general content in the art to which the invention pertains or content that overlaps between embodiments is omitted. The terms 'part, module, component, block' as used in the specification may be implemented in software or hardware, and depending on the embodiments, a plurality of 'parts, modules, components, blocks' may be implemented as a single component, or a single 'part, module, component, block' may include a plurality of components.
[0027] Throughout the specification, when a part is described as being "connected" to another part, this includes not only cases where they are directly connected but also cases where they are indirectly connected, and indirect connections include connections made via a wireless communication network.
[0028] Furthermore, when it is stated that a part "includes" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.
[0029] Throughout the specification, when it is stated that a component is located "on" another component, this includes not only cases where a component is in contact with another component, but also cases where another component exists between the two components.
[0030] Terms such as "first," "second," etc., are used to distinguish one component from another, and the components are not limited by the aforementioned terms.
[0031] Singular expressions include plural expressions unless there is an obvious exception in the context.
[0032] In each step, identification codes are used for convenience of explanation and do not describe the order of the steps; the steps may be performed differently from the specified order unless a specific order is clearly indicated in the context.
[0033] The operating principle and embodiments of the present invention will be described below with reference to the attached drawings.
[0034] In this specification, the "system according to the present invention" may include all various devices capable of performing computational processing and providing results to a client. For example, the system according to the present invention may include both a server and a terminal, or may take the form of either one.
[0035] In the above, the server is a server that processes information by communicating with an external device (including an external server), and may include an application server, a computing server, a database server, a file server, a mail server, a proxy server, a web server, etc.
[0036] In the above, the terminal may include a fixed terminal such as a computer, and the computer may include, for example, a notebook, desktop, laptop, tablet PC, slate PC, etc. equipped with a web browser.
[0037] In the above, the terminal is a mobile device capable of wired or wireless communication, for example, and may include a wireless communication device such as a smartphone, and a wearable device such as a watch, ring, bracelet, anklet, necklace, glasses, contact lens, or head-mounted device (HMD).
[0038] The artificial intelligence-related functions according to the present invention can be operated through a processor and memory. The processor may be composed of one or more processors. In this case, the one or more processors may be general-purpose processors such as a CPU (Central Processing Unit), AP (Application Processor), DSP (Digital Signal Processor), graphics-dedicated processors such as a GPU (Graphic Processing Unit) or VPU (Vision Processing Unit), or artificial intelligence-dedicated processors such as an NPU (Neural Processing Unit). The one or more processors control the processing of input data according to predefined operation rules or artificial intelligence models stored in memory. Alternatively, if the one or more processors are artificial intelligence-dedicated processors, the artificial intelligence-dedicated processors may be designed with a hardware structure specialized for processing a specific artificial intelligence model.
[0039] The predefined operation rules or artificial intelligence models are characterized by being created through learning. Here, being created through learning means that a predefined operation rules or artificial intelligence models configured to perform desired characteristics (or objectives) are created by a basic artificial intelligence model being trained using multiple learning data by a learning algorithm. Such learning may be performed on the device itself where the artificial intelligence according to the present invention is executed, or it may be performed through a separate server and / or system. Examples of learning algorithms include supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but are not limited to the aforementioned examples.
[0040] An artificial intelligence model may be composed of multiple neural network layers. Each of the multiple neural network layers has multiple weight values and performs neural network operations through operations between the results of previous layers and the multiple weights. The multiple weights possessed by the multiple neural network layers can be optimized based on the learning results of the artificial intelligence model. For example, the multiple weights can be updated so that the loss or cost values obtained by the artificial intelligence model during the learning process are reduced or minimized. Artificial neural networks include, for example, CNN (Convolutional Neural Network), DNN (Deep Neural Network), RNN (Recurrent Neural Network), RBM (Restricted Boltzmann Machine), DBN (Deep Belief Network), BRDNN (Bidirectional Recurrent Deep Neural Network), or Deep Q-Networks, but are not limited to the examples mentioned above.
[0041] According to an exemplary embodiment of the present invention, a processor can implement artificial intelligence. Artificial intelligence refers to a machine learning method based on an artificial neural network that enables a machine to learn by mimicking human biological neurons. Methodologies of artificial intelligence can be classified according to the learning method into supervised learning, where input and output data are provided together as training data and the solution (output data) to the problem (input data) is predetermined; unsupervised learning, where only input data is provided without output data and the solution (output data) to the problem (input data) is not predetermined; and reinforcement learning, where a reward is given from an external environment whenever an action is taken from the current state, and learning proceeds in a direction that maximizes such reward. In addition, artificial intelligence methodologies can be classified according to the architecture, which is the structure of the learning model. The architectures of widely used deep learning technologies can be classified into Convolutional Neural Networks (CNN), Recurrent Neural Networks (RNN), Transformers, and Generative Adversarial Networks (GAN).
[0042] The system according to the present invention may include an artificial intelligence engine that includes an artificial intelligence model. The artificial intelligence model may be a single artificial intelligence model or may be implemented as a plurality of artificial intelligence models. The artificial intelligence model may be composed of a neural network (or artificial neural network) and may include statistical learning algorithms that mimic biological neurons in machine learning and cognitive science. A neural network may refer to a model that possesses problem-solving capabilities by changing the strength of synaptic connections through learning, where artificial neurons (nodes) form a network through the connection of synapses. The neurons of a neural network may include a combination of weights or biases. A neural network may include one or more layers composed of one or more neurons or nodes. For example, the device may include an input layer, a hidden layer, and an output layer. The neural network constituting the device can infer a result (output) to be predicted from an arbitrary input by changing the weights of the neurons through learning.
[0043] The processor can create a neural network, train or learn a neural network, perform operations based on received input data, generate an information signal based on the results of the operation, or retrain the neural network. The neural network models may include, but are not limited to, various types of models such as CNN (e.g., GoogleNet, AlexNet, VGG Network), R-CNN (Region with Convolutional Neural Network), RPN (Region Proposal Network), RNN, S-DNN (Stacking-based Deep Neural Network), S-SDNN (State-Space Dynamic Neural Network), Deconvolution Network, DBN (Deep Belief Network), RBM (Restricted Boltzmann Machine), Fully Convolutional Network, LSTM (Long Short-Term Memory) Network, and Classification Network. The processor may include one or more processors for performing operations according to the neural network models. For example, the neural network may include a Deep Neural Network.
[0044] Neural networks include CNN, RNN, perceptron, multilayer perceptron, FF (Feed Forward), RBF (Radial Basis Network), DFF (Deep Feed Forward), LSTM (Long Short Term Memory), GRU (Gated Recurrent Unit), AE (Auto Encoder), VAE (Variational Auto Encoder), DAE (Denoising Auto Encoder), Sparse Auto Encoder (SAE), Markov Chain (MC), Hopfield Network (HN), Boltzmann Machine (BM), Restricted Boltzmann Machine (RBM), Deep Belief Network (DBN), Deep Convolutional Network (DCN), Deconvolutional Network (DN), Deep Convolutional Inverse Graphics Network (DCIGN), Generative Adversarial Network (GAN), Liquid State (LSM) Machine), ELM (Extreme Learning Machine), ESN (Echo State Network), DRN (Deep Residual A person skilled in the art will understand that any neural network may be included, but is not limited to, Network), DNC (Differentiable Neural Computer), NTM (Neural Turing Machine), CN (Capsule Network), KN (Kohonen Network), and AN (Attention Network).
[0045] According to an exemplary embodiment of the present invention, the processor may utilize various artificial intelligence structures and algorithms such as CNN, R-CNN, RPN (Region Proposal Network), RNN, S-DNN (Stacking-based Deep Neural Network), S-SDNN (State-Space Dynamic Neural Network), Deconvolution Network, DBN (Deep Belief Network), RBM (Restricted Boltzmann Machine), Fully Convolutional Network, LSTM Network, Classification Network, Generative Modeling, eXplainable AI, Continual AI, Representation Learning, AI for Material Design, BERT, SP-BERT, MRC / QA, Text Analysis, Dialog System, GPT-3, GPT-4 for natural language processing, Visual Analytics, Visual Understanding, Video Synthesis for vision processing, Anomaly Detection, Prediction, Time-Series Forecasting, Optimization, Recommendation, Data Creation for ResNet data intelligence, but is not limited thereto.
[0046] Meanwhile, the disclosed embodiments may be implemented in the form of a recording medium that stores instructions executable by a computer. The instructions may be stored in the form of program code and, when executed by a processor, may generate a program module to perform the operation of the disclosed embodiments. The recording medium may be implemented as a computer-readable recording medium.
[0047] Computer-readable recording media include all types of recording media that store instructions that can be decoded by a computer. Examples include ROM (Read Only Memory), RAM (Random Access Memory), magnetic tape, magnetic disk, flash memory, optical data storage devices, etc.
[0048] The present invention describes the disclosed embodiments with reference to the accompanying drawings. Those skilled in the art will understand that the present invention may be practiced in forms different from the disclosed embodiments without changing the technical spirit or essential features of the invention. The disclosed embodiments are illustrative and should not be interpreted restrictively.
[0049] In addition, in this specification, "liquidity pool" refers to a pool where token exchange is performed by an automated market maker (AMM) method of a decentralized exchange (DEX), and "staking pool" refers to a pool where tokens deposited for token deposit and reward distribution are managed.
[0050] Additionally, in this specification, the "token liquidity module" may be implemented as a higher-level module comprising at least one of a "swap module" that performs a swap through DEX integration and a "staking module" that processes staking requests.
[0051] In addition, "off-chain rights" are rights that are effective in a system outside the blockchain, and may include, for example, rights to use software / services, license keys, account rights, subscription rights, etc.
[0052] Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.
[0053] The system according to the present invention may be regarded as referring to an overall structure driven by a server, etc., or an overall device configuration driven by a server, etc., and various modules correspond to one component of such a system.
[0054] Figure 1 shows the internal structure of the token module responsible for core roles such as token issuance, verification, and payment, and the inter-component relationships of each component.
[0055] First, when the token module detects a user's payment or transaction request, it forwards the request to the verification module to determine the validity of the request and whether the conditions are met.
[0056] After the validation module reviews the request, if validation fails ("No"), processing is stopped and an error result is returned. If validation succeeds ("Yes"), the process branches according to the type of request. If validation is successful, it branches into the following three paths.
[0057] The first path is for token issuance and distribution. If new tokens need to be issued or distributed according to project conditions, it branches into a smart contract module (3a). Then, the smart contract module processes the "issuance / distribution event", and the token data is recorded in the token DB (4a).
[0058] In one embodiment, the token module performs the creation of payment requests and state management, the reception of payment results and DB recording, and the execution of the actual token issuance / transfer transaction can be performed by the smart contract module.
[0059] The second path is for swapping or staking. If the request is for token exchange (DEX integration) or staking, the request is transmitted to the token liquidity module (DEX integration unit) (3b). The token liquidity module may include a swap module and / or a staking module. In the case of a swap request, it performs the exchange by linking with an external DEX or AMM liquidity pool, and in the case of a staking request, it performs the deposit and reward distribution procedures in an external staking pool. Events related to this may be recorded as "swap events" and / or "staking events," and the corresponding event data is recorded in the token DB (4b). The third path is for a payment request for a real-world asset (RWA, where RWA is an abbreviation for Real-World Asset) or NFT in the real economy (3c). If the request is transmitted to the RWA module, a "payment event" occurs, and this information is also stored in the token DB (4c).
[0060] The final results of each event (issuance / payment, swap / staking, settlement) are systematically recorded and managed in the token DB (4a, 4b, 4c). Through this, the flow and history of each transaction are tracked transparently and consistently.
[0061] In one embodiment, the token DB is an event type (event type ), contract identifier (contract id ), Milestone Identifier (milestone id ), requester's wallet address (wallet addr ), processing module identifier (module id ), target token address (token addr ), amount, status, transaction hash (tx hash ), block number(block no Stores an event record containing ), timestamp, retry count, and error code.
[0062] In addition, for example, the status of a payment event can transition in the order of REQUESTED→APPROVED→SUBMITTED→CONFIRMED→SETTLED, and if an error occurs at any stage, it transitions to FAILED; if the retry condition is met, it can transition back to SUBMITTED instead of FAILED. Additionally, if the number of retries exceeds a threshold, it can be configured to be confirmed as FAILED and switch to an administrator approval or manual re-verification procedure. As such, FIG. 1 clearly illustrates the core data flow and module integration structure of a blockchain-based Web3 utility token system, ranging from a user's transaction / payment request to the processing of various token-related events and the storage of result events.
[0064] Figure 2 illustrates the step-by-step flow of token issuance after a functional unit contract is concluded, and the subsequent deposit, unlocking, and transfer to user wallets of the tokens depending on whether milestones and conditions are met.
[0065] First, once the contract is concluded, contract-based tokens are issued according to the milestones or payment conditions defined in the contract (here, 'contract-based token' refers to a portion of the Genie Token or a corresponding wrapped token, which is managed in an escrow state and is bound to specific contract and milestone conditions). The issued tokens are immediately stored in the token custody module and are securely deposited within the system without being leaked externally.
[0066] In the next step, the system determines "whether the following contract conditions exist."
[0067] If there are any remaining contract conditions to be processed (e.g., additional milestones or phased tasks) ("Next contract exists?" - "Yes"), the status of such conditions is continuously monitored (although only "Next contract condition exists?" is indicated in Fig. 2, the determination includes whether the condition has been met, or, although not shown in the drawing, additional monitoring items regarding the condition's fulfillment may be initiated). When the condition is met, a contract condition fulfillment trigger is generated, and according to the generated trigger, the tokens stored in the storage module are transferred to the user (recipient) wallet. This process is repeated whenever the next condition exists.
[0068] Conversely, if there are no remaining contract conditions ("Next contract exists?" - "No"), meaning all milestones or payment conditions have been completed, the process proceeds through the contract condition completion stage to contract termination, and the token allocation process for the relevant project or stage is completely finished.
[0069] Specifically, when a contract is concluded, the system generates structured data including a contract ID, milestone schedule, payment terms, etc.
[0070] For example, in a project where the Function Point (FP) is calculated as 120, the total reward tokens can be defined as 12,000 GT (Genie Token), and the milestones can be set to three stages (40 FP / 40 FP / 40 FP). In this case, the system can set smart contract conditions to issue 12,000 GT as contract-based tokens upon contract execution and lock them in an escrow wallet, and sequentially transfer 4,000 GT upon approval of the first milestone inspection, 4,000 GT upon approval of the second milestone, and 4,000 GT upon approval of the third milestone to the recipient wallet, respectively. The above FP, total token amount, and milestone distribution ratio can be set variably according to the contract conditions.
[0071] In one embodiment, the contract module is the FP unit price (pfp ), project difficulty coefficient (k d ), urgency coefficient (k u ), quality grade coefficient (k q Store contract parameters including ), and the total reward token amount G, for example, G = FP Х p fp Х k d Х k u Х k q It can be calculated as.
[0072] Also, p fp can be defined as a fiat currency base unit price (e.g., KRW / FP or USD / FP), and a standard conversion rate for converting G into Gini token units (ex rate The final issuance amount can be determined by applying ).
[0073] The aforementioned structured data is stored in an internal database (DB) and simultaneously transmitted to a blockchain module to issue contract-based tokens. At this time, the issued tokens are not immediately transferred to the user's (recipient's) personal wallet, but are securely deposited into an escrow electronic wallet within the platform.
[0074] In one embodiment, the escrow wallet is implemented as a custody address where withdrawals are restricted by a smart contract, and may be configured so that a withdrawal function is called only when both the milestone verification signal and the contract conditions are satisfied. Additionally, a policy may be set to additionally require a multisignature (e.g., n-of-m signature) or an administrator approval flag for high-value payments or risk transactions.
[0075] Subsequently, the backend system determines the existence of contract conditions and continuously verifies the progress of remaining milestones. For example, when an inspection result confirming the completion of a specific milestone is recorded in the database, this information is transmitted to the blockchain via the oracle module. The oracle module detects data from the external world (e.g., database updates, API events from external collaboration tools), converts it into a format understandable by the blockchain, and delivers the converted data to the smart contract.
[0076] In one embodiment, the oracle module forms a "proof bundle" as proof of milestone achievement, comprising at least one of (i) a commit hash of the output repository, (ii) a CI / CD build success log, (iii) a completion status and approver signature of the issue tracker, and (iv) a PDF hash of the inspection result report, and records the hash value of the proof bundle as an on-chain event to enable post-audit.
[0077] In addition, the Oracle module can perform cross-validation between multiple data sources to prevent the possibility of tampering with external data.
[0078] For example, a verification signal can be considered valid only if the same contract condition fulfillment event is detected simultaneously in two or more independent data feeds (e.g., project management server logs, API call history, or external blockchain events).
[0079] This enhances resistance to single-node errors or data tampering attacks, and ensures the reliability of information transmitted to blockchain smart contracts.
[0080] In addition, the oracle module applies a multi-node consensus policy (e.g., approval when t or more out of k nodes match) and records the proof (signature value and timestamp) signed by each node on-chain to enable future auditing. Sanctions such as slashing or weight reduction may be applied to nodes that repeatedly transmit false data, and the oracle configuration can be dynamically scaled in / out according to a predefined policy.
[0081] The smart contract executes conditional release logic based on the information transmitted from the aforementioned oracle module. Specifically, the oracle module detects an event indicating "Inspection Approval Complete," converts it into data understandable by the blockchain network, and transmits this data to the smart contract. Consequently, if the smart contract confirms that the payment conditions defined in the contract have been met, it automatically transfers the tokens stored in the escrow wallet to the user's (recipient's) personal wallet.
[0082] Meanwhile, if a payment transaction fails due to transaction congestion on the blockchain network, a surge in gas fees, or temporary network instability, the smart contract module executes automatic retry logic.
[0083] If retries fail more than a certain number of times, the event transitions to a 'pending' state and is notified to the backend management server, which can then resend the transaction through manual re-validation or an alternative node path.
[0084] This restoration logic plays a crucial role in maintaining the reliability and integrity of token distribution.
[0085] In addition, abnormal transaction detection rules (amount surges, frequency exceedances, abnormal geographic / network patterns) are applied at the backend and contract levels, and automated attacks and abuse are prevented by implementing rate limiting and cooldown policies at the wallet / IP / account level. In the event of a violation of detection rules, the transaction is temporarily suspended and requires two-factor authentication or approval from a management server.
[0086] Smart contracts use state lock flags to prevent reentrancy attacks, and all payment transactions include a nonce and timelock with a single use and expiration time. Additionally, event hashes are stored on-chain to prevent duplicate processing of the same event and block replay attacks.
[0087] Furthermore, smart contracts can apply upgradeable proxy patterns (e.g., Transparent / UUPS Proxy) to securely implement security vulnerability patches or feature extensions under governance approval. Upgrade authority can be delegated or revoked via on-chain governance, and change history and version identifiers are permanently recorded in event logs, enabling post-verification.
[0089] Figure 2 structurally presents the entire flow from contract conclusion to termination, clearly demonstrating the transparency and automation of the process in which tokens are automatically calculated, deposited, and transferred for each milestone, and that tokens are transferred only when conditions are met.
[0090] The present invention allows for the selection of a chain among public, private, or consortium chains based on project requirements (finality time, fees, TPS, security), or minimizes gas fees and processing delays through bridge integration with Layer 2. The status of payment transactions is managed by distinguishing between before and after block finality is reached; prior to finality, it is in a "waiting for approval" state, and upon reaching finality, it transitions to a "payment completed" state, thereby performing user notifications and updating internal settlement records.
[0091] In one embodiment, instead of making payment immediately after milestone approval, a timelock may be set so that payment is made after a predetermined challenge window has elapsed from the time of approval. If a dispute flag is set within the challenge window, payment is suspended, and through the dispute module, the payment may be finally determined as at least one of payment, refund, or partial payment based on the review of the evidence bundle and the results of arbitration.
[0092] In one embodiment, a dispute flag may be transmitted to a smart contract via an oracle after being recorded in an on-chain or off-chain DB by an electronically signed objection request from a demander and / or supplier, or by an administrator / DAO approval transaction.
[0093] Furthermore, to enhance the user experience, gas sponsorship (Metatransactions such as EIP-2771) or transaction relay methods may be supported. Accordingly, recipients can execute payments, swaps, and staking without holding separate native gas, and sponsorship costs may be settled from separate sources such as the platform, project budget, or, if necessary, the on-chain community treasury, depending on the policy.
[0094] Figure 3 illustrates the entire process, from automatically generating proof data upon achieving project milestones based on a smart contract to unlocking tokens and processing reward distribution or refunds.
[0095] First, in the storage unit, a token is issued after the contract is concluded, and the token is immediately switched to a locked state and stored. Subsequently, the verification unit determines whether the conditions are met; if the conditions are not met, the token remains in a waiting state for fulfillment, and the contract may be canceled if necessary or depending on the circumstances. In the waiting state for fulfillment, a step to determine whether the conditions are met is performed periodically or non-periodically upon request.
[0096] When determining whether the conditions are met, if the conditions are satisfied, the relevant fact is transmitted to the processing unit through a certification transmission procedure.
[0097] In the processing unit, token unlocking is performed, followed by the reward delivery stage. If the contract is cancelled, a refund is processed separately.
[0098] After the reward delivery stage, tokens are received at the receiving end, and the process finally terminates.
[0099] Figure 3 consists of storage / verification / processing / receipt stages, respectively, and intuitively illustrates the main flow and conditional branching processing from the creation, locking, condition verification, unlocking, reward payment or refund, token receipt, and the end of the entire process of a smart contract-based automated payment process.
[0101] Figure 4 illustrates the flow of the swap procedure, including request verification, internal approval, integration with an external DEX, and reflection of results, when a user requests a swap of reward tokens (in this specification, "liquidity pool" refers to a pool for AMM-based exchange on a DEX, and "staking pool" refers to a deposit pool for token deposit and reward distribution).
[0102] First, once the milestone is completed in the user's wallet, the reward token is received, and then a request for a swap (exchange) is made.
[0103] The swap request is passed to the swap module, which then sends a verification request to the verification module to confirm the legitimacy of the operation. The verification module reviews this request and returns the verification response (whether it succeeds or fails) to the swap module. If the verification is successful, the swap module undergoes an internal token approval process and requests the execution of the swap from an external DEX or AMM (Automated Market Maker) liquidity pool. Subsequently, if the swap is successfully executed, the external token (i.e., the exchanged token) reaches the swap module, and this token is then transferred back to the user's wallet.
[0104] In one embodiment, the swap module has (i) a maximum slippage tolerance s max , (ii) minimum receipt amount (min out ), (iii) routing method (single pool or multi-hop path), (iv) platform fee rate f p You can create swap parameters including and pass them to an external DEX or AMM liquidity pool. For example, min out The reference price P ref and allow slippage s max min depending on out = amount in Х P ref Х (1 s max It can be calculated as ), and the actual amount received is min out If less than [value], the transaction can be configured to be automatically reverted.
[0105] In addition, the platform fee is before the swap (amount in ( 기준) or after swap (amount out It can be deducted in the selected method among the criteria and distributed to a separate fee wallet.
[0106] If there are remaining internal tokens, a procedure is performed to additionally return the remaining internal tokens to the user's wallet.
[0107] The above-mentioned remaining internal tokens may arise due to settlement differences resulting from, for example, partial execution, rounding during the routing process, fee deduction methods, or rollback of failed transactions, and the remainder may be processed through either an automatic return or a lump-sum return after accumulating a small remainder.
[0108] Specifically, when a swap request is generated from a user's wallet, the request is passed to the swap module, and the swap module queries the verification module to check whether the request is forged or duplicated.
[0109] The verification module determines the legitimacy of the swap request by checking the user's account status, the amount of the requested token held, recent transfer history, as well as whether the request has been processed previously, and returns whether it succeeded or failed to the swap module.
[0110] If verification is successful, the swap module performs an internal approval procedure and requests swap execution by linking with an external DEX (Decentralized Exchange) or AMM liquidity pool; during this process, it connects with an external smart contract through the oracle module.
[0111] Swap requests from user wallets are converted into a JSON-based data structure and transmitted; this converted data structure includes the transaction ID, timestamp, and digital signature value, as well as the requested token quantity and exchange rate, ensuring integrity and traceability.
[0112] Of course, it is not limited to the JSON structure and can also be applied to other formats such as XML.
[0113] When the swap is successfully executed on an external DEX, the exchanged external tokens (e.g., ETH, USDC, etc.) are transferred to the swap module, which immediately sends them to the user's wallet address so that the user can finally receive the exchanged assets.
[0114] The swap module can detect abnormal exchange rate manipulation or slippage excess situations by verifying the exchange rate from the real-time price oracle.
[0115] If a price fluctuation exceeding the specified allowable range is detected, the swap request is automatically canceled, and a "Trading Suspension Due to Market Instability" notification is immediately sent to the user.
[0116] In this case, all failed transactions are recorded in the log and can be referenced during retries or post-audits.
[0117] Finally, if some internal tokens remain during the swap process, a separate settlement procedure is performed to return the remaining tokens to the user's wallet.
[0118] If verification fails or the transaction is rejected by the external DEX, the swap is not executed, and the reason for failure and error code are returned to the user's wallet or retry logic is performed.
[0119] In other words, in Figure 4, the interactions between key entities such as user wallets, verification modules, swap modules, and external DEX or AMM liquidity pools, as well as the flow of data or tokens at each stage, verification and approval procedures, and the result return route are clearly depicted in chronological order. Through this, it can be seen that the swap (exchange) function of the Genie Token system is processed automatically while ensuring security and reliability.
[0120] Additionally, for user convenience, swap and / or staking transactions may be submitted via metatransaction or relay, and can be configured to allow transaction execution even if the user does not hold native gas.
[0122] Figure 5 illustrates a series of staking processes from a user's token staking request to condition verification, staking pool deposit, issuance of proof-of-stake tokens, termination, and return of principal and rewards.
[0123] When a milestone is completed in the user's wallet and the reward token is received, the user can request staking.
[0124] When a user requests staking, the verification module requests proof to validate the request, and the proof response is transmitted to the staking module. If the verification is successful, the staking module executes the staking in the staking pool (external deposit pool) after undergoing an internal token approval process. Subsequently, the user receives their stake (proof tokens, etc.).
[0125] When a mid-term termination request is made—that is, when a user requests termination—unstaking (termination) is executed in the staking module and staking pool, the principal is returned, and the user receives refund tokens.
[0126] Upon expiration of the staking period, the expiration trigger is automatically triggered, token unlocking and reward distribution are executed within the staking module, and the principal and reward tokens are paid into the user's wallet.
[0127] In one embodiment, the staking pool may be composed of at least one of (i) a lock-up type (cannot be withdrawn before maturity or subject to a penalty), (ii) a free type (can be withdrawn at any time), (iii) a fixed reward rate type, and (iv) a variable reward rate type. The reward token may be the same token as the Genie token or a separate reward token, and the reward payment cycle may be set, for example, on a daily / weekly / monthly basis or as a lump-sum payment at maturity.
[0128] Specifically, when a user completes a milestone and receives reward tokens, they can generate a staking request from their wallet. The staking request includes information such as the wallet address, requested quantity, and staking period, and is transmitted to the staking module.
[0129] The staking module queries the verification module to verify the legitimacy and validity of the request, and the verification module determines whether the conditions are met by referring to the user account status, token balance, previous transaction history, etc.
[0130] If the verification result is returned as successful, the staking module deposits a specified quantity of tokens into an external staking pool (deposit pool) after undergoing an internal approval process, and transfers the corresponding proof-of-stake tokens to the user's wallet.
[0131] The above proof-of-stake token may be a derivative token (e.g., sToken) representing the staked stake, and may be burned or returned upon unstaking or maturity.
[0133] If a user requests early termination before the staking period expires, the request is first received by the staking module. The staking module verifies whether unstaking is possible based on the user's wallet address and staking balance information.
[0134] At this point, if rewards have already been distributed, they may be invalidated or configured to be paid out in part according to policy. Once verification is complete, the staking module sends an unstaking request to the external staking pool, and the external pool releases the deposited principal tokens.
[0135] The released principal is sent to the user's wallet address in the form of a refund token, and the fact of the return is recorded on the blockchain through the transaction hash. Additionally, if network delays or transaction failures occur during the release process, the staking module executes retry logic or returns a failure response to the user.
[0136] When the staking period expires, a predefined expiration trigger is automatically triggered. The staking module detects this trigger and sends a token unlock request to the staking pool, which then releases the principal tokens matched to the user account. Simultaneously, the reward distribution logic is executed, and the reward tokens are calculated based on the deposit period, staked quantity, predefined reward rate, and reward policy.
[0137] The calculated reward tokens and principal are sent to the user's wallet via separate transactions, and the hash value of each transaction is recorded on the blockchain ledger to ensure transparency.
[0138] In this case, if there are variable factors affecting the reward rate (e.g., reward rates reflecting market conditions, additional incentives, etc.), the staking module may adjust the final reward amount by reflecting such variable values.
[0139] The calculation of reward tokens is based on the staking period T, deposit quantity A, base reward rate r0, and coefficient of variation. △ An expression composed of r R=AХ(r0+ △ It is calculated according to r)ХT.
[0140] coefficient of variation r can be automatically adjusted based on network liquidity status, project performance, or DAO (Decentralized Autonomous Organization) voting results, and all of these parameters are transparently disclosed on-chain.
[0141] This ensures the fairness and verifiability of the compensation calculation process.
[0142] r0 used in compensation calculation, △ r and the associated weight tables are managed by the parameter registry smart contract, and all changes are announced as on-chain events along with version identifiers. Retroactive application is prevented for payments calculated using parameters from past versions, and user predictability is guaranteed by specifying transition periods between versions.
[0143] Once payment is completed, the system updates its internal status and notifies the user of the maturity and completion of compensation via a notification message.
[0144] If conditions are not met during the verification process, staking is not executed, and an error response is returned to the user's wallet. Additionally, in the event of a transaction failure or network error in the staking pool, the staking module can be configured to perform a retry procedure or return an error message.
[0146] This entire process demonstrates a detailed structure of the entire staking cycle, including the interactions between users, the validation module, the staking module, and external staking pools (deposit pools), as well as staking requests, validation, token deposit, issuance of proof of stake, withdrawal, and maturity processing.
[0148] Figure 6 illustrates the flow of the payment processing procedure, from asset classification, information verification, payment processing, system status update, and notification transmission after payment is completed, when a user requests the purchase of physical assets (RWA) or NFTs, or off-chain rights (e.g., licenses / rights) such as software / service usage rights.
[0149] First, when the user selects an asset or option from the system (1), the issuance control unit classifies the type of asset (RWA / NFT, etc.) (2).
[0150] Here, the issuance control unit and the issuance processing unit are sub-components of the RWA module (or payment module), and the issuance control unit may be configured to perform asset type classification and user request flow control, and the issuance processing unit may be configured to perform balance verification, metadata processing, and on-chain transaction creation / transmission.
[0151] The issuance processing unit preprocesses the information required for issuing the asset (e.g., validation, metadata mapping, etc.) (3) and then presents the price to the user (4).
[0152] When the user approves the purchase (5), the issuance control unit sends a request to the issuance processing unit to check the balance (6). In this process, if the user's balance is insufficient, a notification of insufficient balance is sent to the user and the transaction is stopped (6a).
[0153] If the balance is sufficient, the issuance processing unit sends an asset settlement transaction request to the on-chain (blockchain) (7). On-chain, the transaction is processed and the record is confirmed in the block (8), and the result is delivered to the issuance processing unit (9).
[0154] When the transaction is successfully completed, the system updates the status and notifies the user (10) that the transaction processing is complete, thereby completing the payment process.
[0155] In one embodiment, the delivery and activation status of off-chain rights may be managed as at least one of, for example, ORDERED, ISSUED, ACIVATED, FAILED, and REFUNDED. For example, in the case of a software license, it transitions to the ISSUED status when payment is confirmed, and transitions to the ACIVATED status when the license key issuance or account authorization log is verified. If it does not transition to the ACIVATED status within a specified period, automatic REFUNDED or alternative ISSUED retry logic may be executed.
[0156] Specifically, when a user selects a specific physical asset (RWA) or digital asset (NFT) from the system, the issuance control unit first classifies the type of asset to determine whether it is an RWA or an NFT.
[0157] Next, the issuance processing unit performs preliminary verification procedures necessary for the issuance of the selected asset, which may include verifying the validity of asset information, standardizing metadata, and mapping operations. Based on the results of these preliminary processing, the issuance processing unit presents the asset's price information to the user.
[0158] When the user approves the purchase, the issuance control unit sends a payment execution request to the issuance processing unit, and the issuance processing unit checks the user's wallet balance.
[0159] If the user's balance is insufficient, the transaction does not proceed, and an error message regarding the insufficient balance is delivered to the user. On the other hand, if the balance is sufficient, the issuance processing unit sends an asset settlement transaction request to the blockchain network to execute the settlement of the corresponding asset on-chain.
[0160] When the above transaction is included in a block and confirmed on the blockchain network, the result is returned to the issuance processing unit, and the issuance processing unit records whether the transaction was successful based on this. Subsequently, the system updates the state of the internal database and delivers the fact that the asset purchase and payment have been completed to the user in the form of a notification message.
[0161] After payment is completed, the transaction history of the RWA / NFT asset is recorded on the blockchain in the form of metadata, and the asset's unique identifier (UUID) is mapped to the payment transaction hash.
[0162] The data recorded in this way can be used as reliable evidence for future asset resale, transfer of ownership, or tracking audits of physical assets.
[0163] In addition, the system can be configured to check the status of asset delivery or off-chain registration (e.g., software license activation, account authorization, etc.) through a secondary verification procedure after payment, and to automatically initiate a refund or adjustment process if an anomaly occurs.
[0164] Confirmation of delivery of RWA or Software / Asset-as-a-Service can be completed through a proof bundle consisting of logistics tracking identifiers, third-party appraisal / inspection reports, software license issuance / account activation logs, or notarized electronic signature data, and the hash value of the proof bundle is mapped on-chain along with the transaction hash. In the event of non-delivery within the specified deadline or material defects, the smart contract automatically executes according to predefined scenarios regarding escrow refund, partial refund, or provision of replacement items; if manual arbitration is required, the final status is determined after reviewing the proof via the dispute module.
[0165] The RWA payment and currency exchange functions are integrated with KYC / AML (Know Your Customer / Anti-Money Laundering) procedures, and customer identity verification, Suspicious Transaction Reports (STR), and transaction monitoring logs are stored in accordance with relevant laws and regulations. If Travel Rule integration is required, sender / receiver wallet identifiers and transaction metadata are exchanged within the scope permitted by regulations, and personal information is not directly recorded on-chain but is indirectly verified using hashes / zero-knowledge proofs, etc.
[0166] In this embodiment, exceptional situations that may occur during the payment process are also taken into account. For example, if a payment fails due to insufficient balance, a transaction delay or failure on the blockchain network, or an error occurs during the smart contract call or execution process, the issuance processing unit returns a response message to the user containing the reason for the error, and the transaction is ultimately invalidated.
[0167] This flow illustrates a highly structured diagram of the entire process—from verification steps and balance checks to on-chain execution via smart contracts and final notifications—when a user requests payment using real assets or NFTs. This demonstrates that Genie Token's real-world payment functionality is processed in a transparent and automated manner.
[0169] The claims according to the present invention are as follows. However, it should be noted that this is merely an example.
[0170] An exemplary claim according to the present invention discloses a token operating device linked to a software development project based on a functional unit contract, which calculates and automatically pays digital assets in the form of utility tokens according to the execution stages of the project, comprising: a contract module that calculates a reward amount for each project milestone based on contract information; a token module that performs the issuance, verification, and automatic payment processing of tokens; and a smart contract module that determines whether smart contract execution and payment conditions are satisfied on a blockchain network.
[0171] The above token operating device includes a history management module that records payment conditions and execution history on a blockchain network; wherein the token module includes automatically distributing tokens based on whether a project milestone has been achieved.
[0172] In addition, the token operating device discloses a token operating device that is linked with an external payment system, a decentralized exchange (DEX), and a real asset settlement (RWA) module to provide a function for real-time exchange processing of utility tokens or purchase of real goods.
[0173] In addition, the token operating device includes a verification module that determines the consistency of a user's payment or transaction request and whether payment conditions are met; and a token storage module that controls the storage of contract-based issued tokens in a locked state until conditions are met, and transfers them to the user's wallet when conditions are met.
[0174] Additionally, the token operating device includes a staking module that performs an internal token approval procedure after validating a user's staking request through a verification module, deposits the token into an external staking pool, issues proof tokens regarding the staking stake, returns the principal through unstaking upon early termination, and performs token unlocking and reward distribution upon expiration of the staking period to pay the principal and reward tokens to the user's wallet.
Claims
Claim 1 A token management device linked to a software development project based on functional unit contracts, which calculates and automatically distributes digital assets in the form of utility tokens according to the execution phase of the project, comprising: a contract module that calculates the amount of reward per project milestone based on contract information, storing contract parameters including function points and a unit price corresponding to the function points and defined in fiat currency, calculating the total amount of reward tokens based on the value obtained by multiplying the function points and the unit price, and determining the final issuance amount by applying a standard conversion rate for converting the calculated total amount of reward tokens into token units; a token module that performs token payment processing, automatically distributing tokens depending on whether the project milestones are achieved; a history management module that records payment conditions and execution details on a blockchain network; an oracle module that configures an evidence bundle comprising at least one of a deliverable repository commit hash, a build success log, an issue tracker completion status and approver signature, and an inspection result report hash as proof of milestone achievement, and records the hash value of the evidence bundle as an on-chain event; and smart contract execution on a blockchain network A smart contract module for determining whether payment conditions are met, which determines whether the payment conditions are met based on a verification signal from the oracle module, which is considered valid only when the same contract condition achievement event is simultaneously detected in two or more independent data feeds among project management server logs, call history of external collaboration tools, and external blockchain events, and is configured not to make payment immediately upon milestone approval but to make payment after a predetermined objection period has elapsed from the time of approval, and temporarily suspends payment if a dispute flag is set within the objection period; and a dispute module that, when the dispute flag is set, finally determines at least one of payment, refund, and partial payment according to the review and arbitration results of the evidence bundle.A function that is integrated with an external payment system, a decentralized exchange, and a real asset payment module to provide real-time exchange processing of utility tokens or the function of purchasing real goods, wherein the real asset payment module manages the delivery and activation status of off-chain rights as issuance, activation, and refund statuses, transitions to the issuance status when payment is confirmed, transitions to the activation status when a license key issuance or account authorization log is verified, transitions to the refund status or transitions back to the issuance status for a retry if it is not transitioned to the activation status within a specified period, completes the delivery confirmation of real assets through a delivery confirmation proof bundle composed of at least one of a logistics tracking identifier, a third-party appraisal or inspection report, a software license issuance or account activation log, and notarizable electronic signature data, maps the hash value of the delivery confirmation proof bundle to the on-chain together with the transaction hash, and in the event of non-fulfillment of delivery within a specified period, the smart contract automatically executes according to a predefined scenario among escrow refund, partial refund, and provision of replacement items; and a verification module that determines the consistency of a user's payment or transaction request and whether payment conditions are met, wherein the user's account status, the amount of requested tokens held, A verification module that determines the legitimacy of a request by checking recent transfer history and whether the request has no prior processing history; a token storage module that controls the holding of contract-issued tokens in a locked state until conditions are met and transfers them to a user wallet when conditions are met, implemented as a storage address where withdrawals are restricted by a smart contract, and configured such that a withdrawal function is called only when both a milestone verification signal and contract conditions are met;A token operating device comprising: a staking module that, upon a user’s staking request, performs an internal token approval procedure after validating the validity through the verification module and deposits the token into an external staking pool, issues proof tokens regarding the staking stake, returns the principal through unstaking upon early termination, and performs token unlocking and reward distribution upon expiration of the staking period to pay the principal and reward tokens to the user’s wallet, wherein the reward distribution is calculated by reflecting the staking period, deposit quantity, and basic reward rate, as well as a coefficient of variation adjusted according to network liquidity status or project performance. Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 delete
Citation Information
Patent Citations
Method and server for managementing project
KR1020150134153A
System and Method for Managing Blockchain Reward Token
KR1020240029837A
Server for creating content with cooperation based on blockcahin, server for distributing content and system there of
KR102112288B1
System for providing governance token management service
KR102791308B1
