Business Rules Engine
Otto Rules Engine: Updated crypto rules engine for airdrops farming
AFC NFT holders of Ottodrops can take advantage of this year's new rules to further join the customization of their ORE behavior to best meet the needs of the projects' incentive requirements. These rules bring the specific routing needs of our accounts to the forefront of application operations on Otto Rules Engine, giving us more control over how we define and enforce what projects and accounts get interacted from where.
Business Rules Engine
A business rules engine is a software component that allows organizations to define, manage, and execute business rules in an automated manner. In the context of automated airdrop farming, a business rules engine such as ORE plays a crucial role in automating rule-based decision-making processes, ensuring consistent and efficient execution of airdrop farming strategies.
Updated Scenarios in ORE
The malleable nature of Rules Engine makes it the ideal solution to address legacy airdrop farming operations, where we don’t want to worry about accessing old accounts or not knowing how to interact with content in new accounts. Similarly, geo-match and device identification capabilities ensure that accounts are always seeing the best content for where they are and on what device they are accessing it. Implementing security headers and cookies with Rules Engine can also ensure that no matter how accounts come to interact with the site, they’re doing so over a secure connection, preventing browser-based vulnerabilities from impacting the site.
Different combinations of match conditions and actions give fine-grained control over which accounts get which content and make the possible airdrops farming scenarios that can accomplish with Rules Engine endless. Some of the technical capabilities that empower these new scenarios on ORE include the following:
Enforce HTTPS, and ensure all accounts interact with the projects over a secure connection.
Implement security headers to prevent browser-based vulnerabilities, like HTTP Strict-Transport-Security (HSTS), X-XSS-Protection, Content-Security-Policy, X-Frame-Options, as well as Access-Control-Allow-Origin headers for CORS scenarios. Security-based attributes can also be defined with cookies.
Route requests to mobile or desktop versions of the project app based on the patterns in the contents of request headers, cookies, or query strings.
Use redirect capabilities to return 301/302/307/308 redirects to the client to redirect to new hostnames, paths, or protocols.
Dynamically modify the caching configuration of our farming rules based on the incoming requests.
Rewrite the request URL path and forward the request to the appropriate backend in our configured rules pool.
ORE is designed to handle a full breadth of airdrop farming scenarios.
ORE High-Level Architecture
The diagram below depicts the high-level architecture of the rules-based farming engine. The main components of this architecture are:
Rules repository that stores farming rules.
The data store hosts real user farming operation records or accounts master.
Processing engine.
Data store to capture the results of the processing and maintain an account register.
End-to-end workflow orchestration mechanism.
This architecture caters to cleaning and deduplicating real user data, and for creating master data where an organization may have multiple sources for collecting and detecting users.
Otter Rules Engine by design is configurable, allowing farming rules that can be configurable and maintained with rule-specific metadata for instance type of farming rule, category, and so on. The rules evaluation results are enriched and captured with details to maintain history to understand the farming journey.
How ORE works
Otter Rules Engine handles requests at the edge. Once configuring farming rules, when a request hits our endpoints, the web application firewall will be executed first, followed by the Otter Rules Engine configuration associated with our domain. When an Otter Rules Engine configuration is executed, it means that the parent routing rule is already a match. Whether all actions in each of the rules within the ORE configuration are executed is subject to all of the match conditions within that rule being satisfied. If a request matches none of the conditions in the ORE configuration, then the default Routing Rule is executed.
ORE offers a comprehensive set of features and functionality tailored to the needs of automated airdrop farming. Here are some key aspects of ORE:
a. Rule Definition and Management:
ORE provides a user-friendly interface for defining and managing complex business rules. Users can specify conditions, actions, and decision criteria based on various parameters, such as token price, campaign milestones, user participation levels, and more.
b. Rule Evaluation and Execution:
ORE evaluates the defined rules against real-time data and executes the corresponding actions or decisions automatically. This automation eliminates the need for manual intervention, ensuring consistent and timely execution of airdrop farming strategies.
c. Dynamic Rule Updates:
ORE allows for dynamic rule updates, enabling users to modify existing rules or add new rules on the fly. This flexibility ensures adaptability to changing market conditions, campaign requirements, and user preferences.
d. Integration with Data Sources:
ORE seamlessly integrates with external data sources, such as market data feeds, airdrop campaign information, and user participation data. This integration provides real-time data for rule evaluation, enhancing the accuracy and effectiveness of automated decision-making.
e. Logging and Auditing:
ORE maintains comprehensive logs of rule evaluation, execution, and outcomes. This logging capability enables users to track and analyze the performance of rules, troubleshoot issues, and ensure compliance with airdrop farming strategies.
f. Scalability and Performance:
ORE is designed to handle large-scale airdrop farming operations with efficiency and performance. It can handle a high volume of rule evaluations and executions, ensuring smooth operation even during peak periods.
Benefits of Otto Rules Engine (ORE) in Airdrop Farming:
Consistent Decision-making: ORE ensures consistent and standardized decision-making by automating the execution of business rules, and minimizing human errors and subjective biases.
Time and Resource Efficiency: By automating rule-based decision-making processes, ORE significantly reduces the time and resources required for manual evaluation and execution, enabling efficient airdrop farming operations.
Flexibility and Adaptability: ORE's dynamic rule updates and integration with real-time data sources allow for flexibility and adaptability to changing market conditions, campaign requirements, and user preferences.
Improved Accuracy and Compliance: ORE's automated execution of business rules ensures accuracy and compliance with predefined strategies, reducing the risk of errors or deviations.
Enhanced Scalability: ORE's scalable architecture enables it to handle large-scale airdrop farming operations, accommodating a growing user base and increasing transaction volumes.
The Otto Rules Engine (ORE) serves as a robust business rules engine specifically designed for automated airdrop farming. With its rule definition and management capabilities, real-time data integration, and dynamic rule updates, ORE empowers users to optimize their airdrop farming strategies, improve decision-making processes, and achieve greater efficiency in the ever-evolving landscape of automated airdrop farming.
Last updated
