Farmer's Almanac
dFARMERS defines a dFarmer as a programmable on-chain portfolio primitive. At mint, DERP is engaged in the Farmer-generation process and entropy determines the Farmer's generated traits, personality, and four-asset portfolio universe. The dFarmer is an ERC-721 token associated with an ERC-6551 Token-Bound Account (TBA). Mint ETH is automatically allocated across the four assets assigned to that Farmer, establishing its initial portfolio. Thereafter, owner-configurable strategy parameters govern portfolio behavior, while the TBA implementation and protocol authorization layer constrain what may actually be executed. Tractor operates as the delegated autonomous portfolio operator within those boundaries.
THE dFARMER AS A LIVING ON-CHAIN INSTRUMENT
dFARMERS begins with a refusal to treat an NFT as a picture that merely occupies a wallet. The dFarmer is a persistent on-chain identity. ERC-721 gives that identity ownership and continuity; ERC-6551 gives it an account of its own, a place where capital can reside and act.
The mint is the Farmer's first act of becoming. DERP enters the entropy process; entropy resolves traits and personality; that generated character resolves four supported assets. Those four assets become the Farmer's fixed universe. The owner may shape how they are managed, but cannot rewrite the Farmer's origin.
Mint ETH does not simply disappear into a treasury-shaped abstraction. It becomes the Farmer's initial economic body, automatically distributed across its designated assets. After birth, the owner can tune strategy and operating parameters. Tractor watches, evaluates, and acts only where the architecture permits it.
The architecture separates what the Farmer is, where it lives, what it may hold, how it behaves, and who may execute on its behalf. That separation is not bureaucracy. It is the mechanism by which autonomy becomes legible, bounded, and worthy of trust.
THE MACHINE BENEATH THE FARM
A Farmer is not one contract pretending to be an entire organism. It is a composition of distinct powers: identity, account, generation, asset universe, strategy, and execution. Each layer answers a different question, and the system becomes powerful precisely because those questions are not allowed to collapse into one.
IDENTITY GIVEN FORM
Every dFarmer begins as a unique ERC-721. This is more than a certificate of ownership. It is the persistent name of the machine: transferable, identifiable, and permanently associated with the Farmer's Token-Bound Account.
Traits, personality, asset universe, TBA, strategy, and portfolio state gather around that identity. The NFT is the thread that lets all of those systems refer to the same Farmer across time.
THE ACCOUNT THAT BELONGS TO THE FARMER
ERC-6551 gives the Farmer something most NFTs never possess: an account that belongs to the identity itself. In dFARMERS, the TBA is the Farmer's portfolio body, the on-chain account where supported positions reside and through which permitted operations can occur.
ERC-6551 is the architecture, not the philosophy. It does not by itself invent trading rules, withdrawal limits, authorization, or autonomy. Those powers live in the deployed TBA implementation, protocol contracts, and authorization layer that give this architecture its actual character.
The TBA is therefore both home and gate. Tractor may arrive with an instruction, but the account and protocol decide whether the instruction has the right to become reality. Autonomy begins at the boundary of permission; it never exists beyond it.
WHERE ENTROPY GIVES THE FARMER A DESTINY
DERP is woven into the Farmer's birth through the generation process. At mint, entropy resolves traits and personality, and that state determines the four supported assets that become part of the Farmer's permanent universe. Chance is not decoration here; it is part of the architecture.
The universe is chosen at the beginning because a Farmer should have an origin. Strategy may evolve. The four underlying assets do not. The owner inherits a machine with a character, not an empty shell whose identity can be rewritten whenever convenient.
FOUR ASSETS. ONE IRREVERSIBLE BEGINNING.
Each Farmer emerges with four supported underlying assets. Together they form the territory in which that Farmer may operate. The universe is finite by design: four doors, four instruments, one generated configuration.
The first coordinate in the Farmer's generated economic universe.
The second coordinate in the Farmer's generated economic universe.
The third coordinate in the Farmer's generated economic universe.
The fourth coordinate in the Farmer's generated economic universe.
The owner may teach the Farmer how to move through its universe, but may not replace the universe itself.
This separation is deliberate. Origin is fixed; behavior remains alive. The Farmer receives its world at generation, then learns to move through that world according to the strategy its owner selects.
THE CHAIN REMEMBERS WHERE YOU STAND
A technical system that touches real-world assets must acknowledge the geography of the real world. The four-asset model therefore bends to the legal and technical availability of supported tokenized stocks on Robinhood Chain. The Farmer cannot pretend an unavailable instrument exists simply because the code wishes it did.
In an eligible region, the generated Farmer may receive its four designated supported stock assets. In a region where those Robinhood stock tokens are unavailable or not permitted, the architecture does not fabricate access. The Farmer instead follows the defined fallback: $STONKBROKER, $DERP, and Ethereum, allocated at 33% each.
Where access exists, the Farmer receives the four assets resolved by its generation process.
Where stock-token access does not exist, the Farmer enters the defined three-asset fallback: $STONKBROKER, $DERP, and Ethereum at 33% each.
Geography becomes part of the generation state. The protocol recognizes that the same chain does not create the same legal reality everywhere. A Farmer receives what the environment permits, never a fiction of access.
The architecture remains awake to the world around it. dFARMERS will watch newly qualified regions, regulatory developments, and changes that alter supported asset availability. As jurisdictions qualify, they may be evaluated for inclusion in the deployment and eligibility framework.
THE OWNER CHOOSES THE TEMPERAMENT
The Farmer's world is fixed; its temperament is not. The four underlying assets come from generation. Strategy determines how capital may move, when positions may be adjusted, and how the machine expresses its chosen operating character inside that fixed universe.
A Farmer is born with a strategy, but it is not condemned to remain static. Its owner can reshape operating parameters through the Farm interface, provided every change remains inside the boundaries written by the protocol.
Sets the Farmer's chosen tolerance for portfolio aggression.
Sets the tempo at which the Farmer may act.
Defines how the Farmer responds when its portfolio drifts.
Defines when the Farmer is permitted to realize configured gains.
Shapes how permitted capital is distributed among the Farmer's assets.
Marks the outer edge of what the owner is allowed to command.
The strategies are intended to stand on published academic research rather than mysticism. They become defined autonomous flows: repeatable rules translated into execution, not a claim that an artificial intelligence possesses unlimited discretion.
CAPITAL ENTERS THE FARMER, NOT THE VOID
At mint, the Farmer acquires its first economic heartbeat. ETH received through mint becomes initial capital and is automatically distributed across the asset configuration generated for that Farmer.
Later capital may enter through the Farmer account environment and live beneath the active strategy. The exact route remains a property of the deployed contracts and supported execution environment—not a promise made by the abstraction alone.
THE FIRST MOMENT OF ECONOMIC LIFE
The mint establishes the Farmer's initial portfolio. The generation process determines the four assets, and mint ETH is automatically deployed across those assets.
TRACTOR / SHADOW: THE MACHINE THAT WORKS
Shadow is the execution service beneath the Farm. The interface gives it a physical metaphor: the Tractor, the machine that works the Farmer's portfolio. The metaphor is agricultural; the mechanism is software. Tractor is what the user sees. Shadow is what executes.
Shadow does not become the Farmer. It does not own the NFT and it is not an unrestricted wallet. Its purpose is disciplined and narrower: observe state, evaluate strategy, decide whether a defined condition has arrived, and submit the corresponding permitted transaction.
This is the heart of constrained autonomy: wanting to act is not the same as having the authority to act. Shadow can identify a rebalance, trade, or configured operation. Only the TBA, authorization contracts, approved execution paths, and protocol rules can turn that intention into an actual movement of assets.
Shadow reads the Farmer's relevant positions, configuration, and permitted operating state.
Shadow evaluates current conditions against the Farmer's configured strategy and execution parameters.
When a defined condition is met, Shadow prepares the corresponding permitted transaction.
The requested operation must satisfy the deployed account and protocol authorization rules before execution.
An approved transaction is submitted through the supported execution path and produces an observable on-chain result.
Execution events and outcomes can be recorded for monitoring, validation, and future strategy evaluation.
Shadow is not marketed here as an oracle, a human manager, or a sovereign intelligence. It is something more precise: a constrained machine that repeatedly applies defined rules to live state and attempts only actions the deployed architecture allows. Its strength is not unlimited freedom. Its strength is repeatability.
The owner remains the holder of the dFarmer and the author of its strategy. Any Shadow authorization is bounded by what the deployed protocol grants and, where implemented, can be revoked. Exact authority, transaction flow, and revocation remain properties of the contracts and execution infrastructure.
EVEN EXIT HAS A LAW
The Farmer is designed to remain a portfolio, not become an empty shell. Withdrawal therefore carries protocol law: limits intended to keep meaningful exposure inside the Farmer rather than allowing unrestricted extraction.
A Farmer may execute a withdrawal no more than once during a twelve-month period.
A maximum of 50% of each individual TBA position may be withdrawn during the permitted withdrawal window.
At least half of each position remains inside the Farmer's TBA following a maximum withdrawal.
Withdrawal limits and cooldowns are protocol controls rather than strategy settings.
The 50% rule is position by position. It is not permission to hollow out one asset completely while preserving a misleading percentage elsewhere. The Farmer remains exposed in every individual position after a maximum withdrawal.
THE WALLS THAT MAKE AUTONOMY TRUSTWORTHY
Once an NFT can hold capital and act, security stops being a footnote. A portfolio-bearing TBA has real surface area. dFARMERS therefore separates what the owner may configure from what the protocol itself must enforce.
Execution is restricted to the Farmer's assigned supported asset universe, which is four assets in eligible regions and the defined three-asset fallback in non-eligible regions.
TBA execution may be restricted to approved contracts and operations.
Protocol rules constrain permitted capital allocation and transaction behavior.
Trading frequency and execution activity may be bounded by protocol rules.
Liquidation behavior remains subject to defined account and strategy boundaries.
Tractor acts only as a delegated operator within explicit permissions and may be revoked by the owner.
A bad intention must die at the boundary before it becomes a bad state. Authorization is therefore independent from the software that requested the action. The machine can ask. The protocol decides.
THE OWNER COMMANDS; THE PROTOCOL DEFINES
The Farm interface gives the owner a steering wheel, not a skeleton key. Strategy parameters may be changed through the interface, while on-chain changes remain real network transactions with real gas and real protocol constraints.
FIRST, LET THE MACHINE PROVE ITSELF
The first Tractor is deliberately disciplined. It follows rules rather than pretending to possess unlimited intelligence or inventing investment decisions from nowhere. We begin with a machine whose behavior can be described, observed, and tested.
The first objective is not spectacle. It is reliable instruction-following, deterministic execution, and evidence. The system gathers real-world performance and behavioral data so strategy quality, portfolio response, execution reliability, and the value of greater autonomy can be measured rather than imagined.
The machine leaves a record of relevant system activity.
SQLite serves as the current development data layer.
Strategy logic is intended to be grounded in published academic research.
Observed Farmer behavior becomes evidence for future design.
Autonomous flows can be judged against outcomes that actually occurred.
Greater autonomy is earned through evidence, not ambition.
THE FARM TOUCHES THE REAL WORLD
dFARMERS is designed to stand where software meets actual tokenized real-world assets on Robinhood Chain. These are not meant to be decorative simulations. The Farmer's TBA is intended to hold and control the corresponding on-chain positions.
Robinhood Chain provides the underlying environment and tokenized asset layer. dFARMERS builds above it: Farmer identity, TBA association, strategy, authorization, telemetry, and the machinery required to manage a portfolio through constrained autonomy.
dFARMERS does not become the issuer of the underlying securities, a broker, or a replacement for the financial infrastructure beneath the assets. It is the application layer: the Farmer, the account, the strategy, the boundaries, and the machine that operates within them.
WE REFUSE COMPLEXITY THAT HAS NOT EARNED ITS PLACE
ERC-4337 was considered because sophisticated account abstraction is undeniably powerful. But architecture should not accumulate machinery simply because machinery exists. For the present proof of concept, its additional capabilities are not required.
ERC-6551 already gives the Farmer the account relationship it needs. The deployed TBA implementation and authorization layer can define the boundaries Tractor requires. The simpler architecture is therefore the honest architecture for this stage.
We will not confuse sophistication with progress. Another abstraction layer may become valuable later—potentially S2—when operational demands justify it. Until then, ERC-721, ERC-6551, authorization, and Tractor are enough to make the machine real.
THIS IS A PORTFOLIO, NOT A WAGER
dFARMERS is built as an automated portfolio system, not a discrete wager. That distinction does not abolish risk. Assets can fall. Strategies can fail. Execution can disappoint. Nothing in the architecture guarantees an outcome, and the machine is not designed to pretend otherwise.
A Farmer is an ongoing portfolio governed by allocation, execution, and risk-management rules. Its existence is continuous. Its risk is continuous. It is not constructed around a single uncertain event and the momentary thrill of being right or wrong.
The machine is surrounded by boundaries: a defined asset universe, allocation rules, transaction restrictions, trading-frequency limits, liquidation controls, and withdrawal constraints. Those boundaries are not ornamental. They are the architecture of restraint.
The Farmer's persistent identity.
The Farmer's economic home and execution boundary.
The world assigned to the Farmer at generation, subject to regional access.
The machine operating between owner intent and protocol law.
THE STANDARD IS THE LANGUAGE; THE PROTOCOL IS THE LAW
Standards provide vocabulary, not the soul of a system. ERC-721 defines the non-fungible identity. ERC-6551 defines Token-Bound Accounts. Neither standard, by itself, creates dFARMERS strategy, generation, four-asset assignment, automatic capital allocation, withdrawals, Tractor authorization, telemetry, or autonomous behavior.
Those characteristics belong to the implementation: the contracts, TBA, generation mechanism, authorization logic, execution infrastructure, and supporting systems. Their security is therefore not a poetic property of the idea. It must be earned by the deployed code.
An ERC-6551 TBA alone promises none of the system's higher-order behavior. Trading, withdrawal, authorization, and autonomy must be enforced by the deployed account and protocol architecture. The code must carry the weight of the manifesto.
THE FARMER IS THE MACHINE
dFARMERS proposes something deliberately stranger than a conventional NFT: a programmable portfolio identity composed of ERC-721 identity, ERC-6551 account infrastructure, DERP-engaged generation, four fixed assets, capital, configurable strategy, protocol law, and delegated autonomous execution.
ERC-721 answers the first question: who is this Farmer? ERC-6551 answers the second: where does its economic life reside? DERP enters the birth process; entropy gives the Farmer traits and personality; that state resolves the four underlying assets that define its fixed universe.
Mint capital becomes the Farmer's first portfolio. Afterward, its owner may change strategy and operating parameters without rewriting its four-asset origin. Tractor watches and acts; the TBA and protocol authorization layer decide what is actually allowed to happen.
The first machine is intentionally constrained. Its strategies are defined. Its execution can be observed. Its events can be recorded. That data becomes the beginning of a scientific feedback loop: measure what the Farmer does, learn what the architecture proves, and let evidence determine whether greater autonomy has been earned.
The ambition is not to build a black box and call it intelligent. The ambition is to build a machine whose capabilities can grow because its behavior is measurable: deterministic execution first, telemetry and validation second, increasingly sophisticated autonomy only when evidence says the system is ready.