Franklin BENJI Transfer Agent vs Chainlink SmartData Proof Map
Verified Fact Boundary
1. Franklin's BENJI page says the fund's transfer agent maintains the official record of share ownership through a proprietary blockchain-integrated system. 2. Franklin's DevHub publishes BENJI-related contract addresses across multiple public blockchain networks. 3. The Franklin prospectus says all fund and shareholder records in the blockchain-integrated recordkeeping system are under the full and complete control of the fund's transfer agent. 4. Chainlink SmartData documentation describes Proof of Reserve feeds, NAVLink feeds and SmartAUM feeds as SmartData product categories. 5. Chainlink SmartData documentation says users are responsible for reviewing feed quality before integrating feeds into smart contracts. 6. These sources do not prove that a token address alone establishes legal ownership, that a feed fits every collateral use case, or that future records, reserves or NAV values will remain unchanged.
Show less
Decision Matrix
Article table: scroll horizontally, or focus the table area and use the arrow keys.
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Ownership record | the legal record may be controlled by a transfer-agent system rather than inferred from a public token display | identify the official recordkeeper before treating a token as a share record | private investor status and dispute priority |
| Contract address | public addresses help identify onchain objects but do not replace investor eligibility evidence | record chain, token address, module type and source page before integration | future deployments, migrations and address confusion |
| Feed category | reserve, NAV and AUM feeds answer different valuation questions | name the SmartData category and expected unit before consuming a feed | methodology changes and custom-feed assumptions |
| Integrator duty | data feeds are not a blanket warranty for a protocol using them | review quality, heartbeat, update behavior and failure handling in the consuming contract | oracle outage, stale rounds and downstream liquidation logic |
| Stop condition | collateral use should pause when ownership record and data-feed meaning are mixed | stop before accepting collateral if record priority, address, feed unit or update behavior is unclear | future legal, tax and redemption outcomes remain unknown |
Source Map
- Franklin Templeton Digital Assets: Invest with Benji (franklin-benji-overview)
- Franklin Templeton Digital Assets: Benji DevHub (franklin-benji-contracts)
- Franklin Templeton: Franklin OnChain U.S. Government Money Fund Prospectus (franklin-fobxx-prospectus)
- Chainlink Documentation: SmartData (chainlink-smartdata)
Control Notes
1. Ownership record
Ownership record is the point where public documentation must become an operating rule. In this package, it means the legal record may be controlled by a transfer-agent system rather than inferred from a public token display. The practical action is to identify the official recordkeeper before treating a token as a share record. The unresolved edge is private investor status and dispute priority, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
2. Contract address
Contract address is the point where public documentation must become an operating rule. In this package, it means public addresses help identify onchain objects but do not replace investor eligibility evidence. The practical action is to record chain, token address, module type and source page before integration. The unresolved edge is future deployments, migrations and address confusion, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
3. Feed category
Feed category is the point where public documentation must become an operating rule. In this package, it means reserve, NAV and AUM feeds answer different valuation questions. The practical action is to name the SmartData category and expected unit before consuming a feed. The unresolved edge is methodology changes and custom-feed assumptions, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
4. Integrator duty
Integrator duty is the point where public documentation must become an operating rule. In this package, it means data feeds are not a blanket warranty for a protocol using them. The practical action is to review quality, heartbeat, update behavior and failure handling in the consuming contract. The unresolved edge is oracle outage, stale rounds and downstream liquidation logic, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
5. Stop condition
Stop condition is the point where public documentation must become an operating rule. In this package, it means collateral use should pause when ownership record and data-feed meaning are mixed. The practical action is to stop before accepting collateral if record priority, address, feed unit or update behavior is unclear. The unresolved edge is future legal, tax and redemption outcomes remain unknown, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
Known Unknowns
- private investor status and dispute priority
- future deployments, migrations and address confusion
- methodology changes and custom-feed assumptions
- oracle outage, stale rounds and downstream liquidation logic
- future legal, tax and redemption outcomes remain unknown
Practical Takeaway
Franklin BENJI and Chainlink SmartData answer different tokenized-asset evidence questions. Franklin's BENJI materials and prospectus say the fund's transfer agent maintains the official record of share ownership through a proprietary blockchain-integrated system, while Chainlink SmartData describes feeds such as Proof of Reserve, NAVLink and SmartAUM as data products that integrators must evaluate for their own contracts. The decision is to separate legal ownership record, public token address, data-feed category, reserve or NAV meaning, update behavior and integration responsibility before using an RWA token as collateral or reporting evidence. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.
Topic hubs & tools:Compare any two exchanges