Blockchain Account Token Security via Smart Contract Expiration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current third-party login systems lack user control over account tokens, as these tokens are often shareable and do not expire, leading to unauthorized access and a cumbersome process for users to manage permissions.
Innovation Solution
A blockchain-based system for secure storage and distribution of account tokens, where usage rules are enforced through smart contracts, ensuring only authorized entities can access and use tokens, which expire periodically, requiring websites to obtain new tokens for each use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional third-party login systems are used to enable easy user registration and login, then user convenience and registration speed are improved, but user control over account tokens deteriorates and security risks increase
Solution Approach 1:
The patent introduces a blockchain-based intermediary system that mediates between users and third-party services. The blockchain stores account tokens in a decentralized manner, preventing any single entity (including third-party services) from having complete control. Smart contracts act as automated intermediaries that enforce usage rules and expiration policies, thereby maintaining user convenience while restoring user control over token distribution and access.
Solution Approach 2:
The patent segments control over account tokens by separating storage (on blockchain), management (via smart contracts), and usage (by authorized entities). This segmentation prevents centralized control by third-party services while maintaining ease of operation through automated processes. Users retain ultimate control through the decentralized nature of blockchain storage.
2Adaptability or versatility
If account tokens are made shareable and persistent for website access, then website functionality is improved, but unauthorized access and token misuse increase
Solution Approach 1:
The patent makes account tokens dynamic by implementing automatic expiration through smart contracts. Tokens are no longer static and persistent but have defined lifecycles with start and end times. This dynamic approach allows tokens to be shared and used during authorized periods while automatically becoming invalid, thereby preventing long-term unauthorized access and token misuse.
Solution Approach 2:
The patent applies preliminary anti-action by embedding expiration logic and usage rules directly into smart contracts before tokens are distributed. These pre-programmed constraints prevent unauthorized access and misuse by design, rather than relying on post-distribution control. The harmful potential of shareable tokens is counteracted in advance through automated enforcement of usage policies.
3Adaptability or versatility
If users manually manage account token permissions through third-party services, then permission control capability is improved, but time consumption and complexity increase
Solution Approach 1:
The patent implements self-service by enabling users to pre-configure usage rules and expiration policies for their account tokens through smart contracts. Once configured, the system automatically manages token distribution, validation, and expiration without requiring user intervention. This eliminates the time-consuming manual process of navigating third-party service settings while maintaining comprehensive permission control capability.
Solution Approach 2:
The patent applies preliminary action by requiring users to set up their permission preferences and token policies in advance through smart contract configuration. These preliminary actions establish automated rules that govern all future token interactions, eliminating the need for repeated manual permission management. The system proactively handles authorization decisions based on pre-defined criteria.
Data Source
AI summary
A method for secure storage and distribution of account tokens includes: storing blockchain data comprised of a plurality of blocks, each block including at least a block header and one or more data values, where each data value includes at least an identification value, an account token, and one or more usage rules; receiving a login request including at least a specific identification value and a set of credentials; identifying a specific data value included in the blockchain data where the included identification value corresponds to the received specific identification value; validating the set of credentials based on the identified specific data value and access to the account token included in the specific data value based on the included one or more usage rules; and transmitting the account token included in the identified specific data value in response to the login request upon successful validation.