[Shutter DAO 0x36 Impact Pilot Program Round 1 - Proactive Grant - PEN–Octant Integration Proof: Yield Routing, Refund Solvency & Governance Readiness

PEN–Octant Integration Proof: Yield Routing, Refund Solvency & Governance Readiness

1. Application

Applicant name or organization: CreativesOnchain

Primary contact / forum handle: CreativesOnchain — @CreativesOnchain

Team: Micheal Dean — Technical Lead

Social Handle (X): Blockchain for Creatives (@cr8tivesonchain) / X

GitHub Profile: intelliDean (Michael Dean Oyewole) · GitHub

MVP Repository: GitHub - intelliDean/penoctant: Foundry integration proof verifying yield-donating ERC-4626 compounders between Shutter’s Perpetual Endowment Network (PEN) and Octant on Ethereum mainnet fork. · GitHub

Demo Video: https://drive.google.com/file/d/1DOR9QTQ606d8DbfuZFhp85oVNr-Ro8pe/view?usp=drivesdk

How did you hear about this grant program? Through the Shutter DAO 0x36 Impact Pilot announcement.

Wallet address for payment (if approved): 0x1C9b94ef19bce5CAB6CC7Fd458C30d09D431022B

Application type:

  • :check_box_with_check: Round 1 — Proactive grant for defined future work

Round 1 objective (select one):

  • :check_box_with_check: Objective 6 — Advance Shutter PEN Adoption, Operations, and Funding Readiness

Contribution area:

  • :check_box_with_check: Research or technical work

2. The Shutter need or opportunity

What specific need, opportunity, or gap does this contribution address?

Shutter’s Perpetual Endowment Network (PEN) is intended to help fund public goods over the long term. The idea is to put treasury capital to work, use the returns to support worthwhile projects, and still maintain the ability to honor SEAT-holder refunds.

But depositing treasury funds into a yield strategy is only half the job.

The more difficult question is what happens afterward.

Consider a situation where PEN has deposited USDC into a yield-generating vault. The strategy earns a return, and the community approves funding for a project. At that point, the operators need to know where the earnings actually are and how to make them available for distribution.

With Octant’s yield-donating strategies, profits can be minted as new shares to a designated donation recipient rather than simply increasing the value of the principal depositor’s shares.

That creates an important distinction for PEN. The strategy might have generated a return, but PrincipalManager may not recognize those earnings as available yield until the donation shares have been redeemed and the proceeds transferred into PEN.

If the recipient or collection process is misunderstood, contributors could prepare a funding operation expecting money that is not yet available in the relevant contract. If the donation recipient is configured incorrectly, the earnings could end up under the control of an unintended address.

There is also the refund side of the equation.

A SEAT holder may request a refund when much of PEN’s capital is invested. Even if the treasury’s accounting shows sufficient assets, the strategy still needs to provide the liquidity required for that withdrawal. If the underlying vault restricts withdrawals, experiences a loss, or temporarily cannot supply enough assets, the refund may fail.

The concern is not simply whether PEN can deposit USDC into an ERC-4626 vault. It is whether the entire flow works correctly when real accounting, yield ownership, liquidity requirements, and governance permissions are involved.

These are potential integration and operational risks, not claims that PEN has already suffered a loss or misdirected funds.

PEN’s public repository acknowledges the testing gap: its generic ERC-4626 integration has been tested using demo vaults, while its expected production direction includes Octant-compatible strategies.

Our project addresses that gap by providing a reproducible integration assessment covering the full PEN capital lifecycle, using a specific Octant yield-donating strategy configuration.

Why is it relevant to Shutter now?

PEN already has deployed contracts on Ethereum, and its architecture supports investing treasury assets through ERC-4626 vaults.

Shutter has also previously explored Octant as part of its broader treasury strategy. However, a successful integration with the DAO’s treasury does not automatically demonstrate that the same strategy behaves correctly with PEN’s principal accounting, SEAT refunds, and governance execution process.

The risk of postponing this work is that these questions remain unanswered until contributors are preparing an actual allocation or funding operation.

Testing those behaviors beforehand is considerably easier than discovering an integration limitation after capital has been committed.

We are not arguing that PEN must deploy an Octant vault immediately. The value is giving contributors reliable technical evidence before they decide whether this particular configuration is suitable.

Our goal is to make that evaluation reproducible, rather than leave future operators to piece together assumptions from separate contracts and documentation.

What specific demand signal supports this work now?

We have three concrete signals supporting this contribution.

1. PEN’s documented testing limitation

PEN’s repository states that its current vault integration tests use demo vaults, while production is expected to involve Octant v2-compatible vaults.

Source: GitHub - shutter-network/perpetual-endowment-network · GitHub

2. Shutter’s previous Octant treasury work

Shutter has already explored an Octant integration for treasury management, establishing a relevant strategy family and operational reference.

Source: Update: Octant v2 Pilot to Optimize Treasury & Strengthen Ecosystem

3. Our working MVP

Rather than submitting only a technical idea, we built an initial Foundry integration test package.

The MVP exercises PEN’s deployed Ethereum contracts together with a locally created Octant strategy using existing mainnet infrastructure.

The repository includes four passing tests covering deposit and yield routing, yield realization, a simulated vault-funded refund, unauthorized reporting, and incorrect donation-recipient behavior.

The GitHub Actions workflow successfully ran the four tests on October 6, 2026.

MVP: GitHub - intelliDean/penoctant: Foundry integration proof verifying yield-donating ERC-4626 compounders between Shutter’s Perpetual Endowment Network (PEN) and Octant on Ethereum mainnet fork. · GitHub

Test results: penoctant/RESULTS.md at main · intelliDean/penoctant · GitHub

CI evidence: chore: add demo/ to .gitignore · intelliDean/penoctant@95606d8 · GitHub

Demo video: https://drive.google.com/file/d/1DOR9QTQ606d8DbfuZFhp85oVNr-Ro8pe/view?usp=drivesdk

These signals establish a specific technical need and a feasible approach. They do not constitute a commitment from PEN governance to adopt the integration.

Who benefits from the outcome, and how?

PEN developers will receive reusable integration tests that go beyond demonstrating basic ERC-4626 compatibility.

SEAT holders and governance reviewers will be able to examine how a proposed strategy handles principal, donated yield, liquidity, and refunds before deciding whether it deserves further consideration.

Future PEN operators will have documented transaction sequences, configuration requirements, and failure cases to consult when preparing treasury operations.

The work will also remain open source, so future contributors can extend the test package without starting the same integration investigation from scratch.

Value pathway (required for Round 1)

Which value pathway does this contribution advance?

  • :check_box_with_check: Validated path toward a pilot, integration, or repeatable workflow

The project also contributes durable public-goods value by making PEN’s integration assumptions testable and publicly reviewable.

It does not depend on generating revenue during the grant period.

Who is the relevant decision-maker, operating owner, funder, partner, or beneficiary group?

The relevant decision-making group is Shutter PEN’s SEAT-holder governance.

PEN developers, technical contributors, and future treasury operators are the immediate beneficiaries.

Our work does not require control over production funds, a commitment from Octant, or prior approval of a specific investment strategy.

Any live integration or treasury allocation remains subject to the appropriate governance and risk-review process.

What problem are they solving, and what evidence supports the value of addressing it?

The central problem is the gap between a vault being technically callable and the vault being operationally suitable for PEN.

Our existing MVP has already demonstrated several useful behaviors under controlled conditions.

First, a SEAT purchase can result in USDC being deposited into the tested strategy, with the resulting principal shares held by PrincipalManager.

Second, when synthetic profit is introduced and the actual Octant reporting function is executed, donation shares are minted to the configured PEN Safe. The principal shares remain separate.

Third, the Safe can redeem those donation shares and transfer the proceeds to PrincipalManager, making the funds visible to PEN’s available-yield accounting. The MVP also demonstrates a SEAT refund that requires withdrawal from the strategy rather than relying solely on idle USDC.

Finally, the negative tests demonstrate that an unauthorized reporting call fails and that earnings sent to a different donation recipient are not incorrectly counted as available to PEN.

All four tests have passed in the published CI workflow.

However, we want to be precise about what this proves.

The MVP runs on a local Ethereum mainnet fork. It introduces synthetic profit, impersonates authorized accounts for testing, and disables the strategy’s health check during the unusually large synthetic-profit scenarios.

These tests establish that the demonstrated transaction sequences can work under those conditions. They do not prove production security, universal liquidity, or that every required governance operation has been exercised through an approved proposal.

The remaining work is to test the less convenient conditions: what happens when losses occur, withdrawals are restricted, normal reporting controls remain enabled, or governance must execute the required operations through its actual permissions.

That is the work for which we are requesting funding.

What Shutter product, deployment, service, or capability would this contribution advance?

Shutter Perpetual Endowment Network (PEN).

The project focuses on the following components:

  • PEN’s PrincipalManager, which holds and accounts for treasury assets.

  • PEN’s BondingTranche and SEAT refund mechanism.

  • The PEN governance Safe and its execution permissions.

  • A candidate Octant Morpho/Steakhouse USDC yield-donating strategy.

The work is limited to one explicitly documented integration route. It is not a general-purpose vault integration platform.

What decision, implementation step, or next action should this contribution enable, and by when?

By November 07, 2026, we will deliver a reproducible integration assessment that PEN contributors can use to answer a specific question:

Does the tested Octant configuration support PEN’s intended principal, yield, funding, and refund operations under the documented conditions, and what limitations must be addressed before considering live use?

The resulting assessment will identify:

  • The exact contract versions and configuration tested.

  • Which operations succeeded and under what conditions.

  • Whether reporting, withdrawal, or accounting behavior introduces a blocker.

  • The permissions and transaction steps required for the supported workflow.

  • What remains outside the tests and requires separate review.

The outcome may be a validated technical path or a documented incompatibility.

Either result will be supported by executable evidence.

The DAO will retain responsibility for deciding whether to proceed with any integration or capital allocation.

What evidence will show progress beyond outreach, general interest, or a speculative concept?

We have already published the initial MVP. The funded work will deliver the following additional evidence.

Deliverable 1 — Deterministic integration test environment

We will pin the Ethereum fork block and verify the tested implementation identities, deployment assumptions, and relevant configuration.

The existing tests currently use known contract addresses but do not enforce a fixed fork block by default. We will address that reproducibility limitation.

Acceptance: Another developer can run the published test suite against the specified fork state and independently inspect the same contract configuration and results.

Deliverable 2 — Reporting, loss, and liquidity-failure tests

We will extend the MVP to cover realistic reporting conditions with normal health checks enabled, controlled loss scenarios, withdrawal restrictions, and their effects on PEN’s accounting and refund behavior.

We will clearly separate tests using real deployed vault behavior from cases requiring controlled synthetic conditions or test fixtures.

Acceptance: The tests produce reproducible results explaining which operations succeed, fail, or remain unverified under the specified conditions.

Deliverable 3 — Governance execution-path verification

The MVP currently uses local impersonation to exercise privileged operations.

We will extend the assessment to examine how the supported operations pass through PEN’s Safe and governance execution path, including relevant permissions and transaction encoding.

Where a complete governance path can be reproduced, we will provide the executable test. Where it cannot, the report will explicitly identify the unverified step and provide the required transaction data and limitations.

Acceptance: Reviewers can distinguish operations exercised through the actual governance path from those tested through direct authorized-account impersonation.

Deliverable 4 — Final integration report and operator handover

We will publish a concise report covering the configuration, test results, principal and yield accounting, withdrawal behavior, required roles, transaction recipes, known limitations, and the recommended next technical step.

The report will compare the additional work with PEN’s existing vault tests and Shutter’s earlier Octant treasury pilot to make the incremental contribution clear.

Acceptance: A technically competent contributor can reproduce the tests and understand whether the selected configuration is ready for further governance review or requires additional work.

A reproducible incompatibility with a clearly identified cause will be a valid technical finding. An unfinished setup or unexplained test failure will not count as successful delivery.


3. Funding request

Amount requested

$1,800 equivalent, payable in USDC + SHU under the program’s approved payment terms.

Proposed use of funds / budget rationale

We have already built and published the initial MVP. We are not requesting payment for the four existing tests or the work already completed.

The requested funding covers the additional validation, failure testing, governance-path verification, and final technical handover.

Remaining work Budget
Pin fork and implementation identities; strengthen reproducibility $250
Realistic reporting, loss, liquidity, and accounting failure tests $600
Governance and Safe execution-path verification $650
Final results, operator guide, and handover $300
Total $1,800

The budget is deliberately limited to one candidate configuration.

We will reuse the existing code and testing infrastructure rather than build a new frontend, deploy a new production contract, or expand into unrelated vault strategies.

Milestones

November 6, 2026 — Progress checkpoint

Publish the deterministic test configuration, additional reporting and failure cases, and initial governance-path findings.

November 15, 2026 — Final delivery

Deliver the agreed test suite, reproducible execution evidence, integration assessment, and operator handover.

Payment structure

We propose the program’s standard proactive-grant payment structure:

  • First tranche: $900 equivalent following DAO approval.

  • Final tranche: $900 equivalent after the agreed work is delivered, reviewed, and separately approved by the DAO.

Maintenance and scope

The completed work will remain publicly available in the project repository. Existing third-party license obligations will be preserved.

We will provide 30 days of support for defects and reproducibility problems within the delivered scope.

The grant does not include production treasury transactions, a new yield strategy, modifications to PEN’s live contracts, a frontend, a comprehensive security audit, or any guarantee of future withdrawal liquidity.


4. Prior compensation and disclosures

Have you, your organization, or a related party received or requested compensation for this work from Shutter or another source?

  • ☐ No

  • ☐ Yes — disclose source, amount, compensated scope, and relationship to this application.

Existing-work disclosure:

The initial MVP was developed and published before this application.

Repository: GitHub - intelliDean/penoctant: Foundry integration proof verifying yield-donating ERC-4626 compounders between Shutter’s Perpetual Endowment Network (PEN) and Octant on Ethereum mainnet fork. · GitHub

This proposal is for additional, clearly defined work beyond the existing implementation. We are not asking the DAO to pay for the initial four passing tests a second time.

Prior compensation declaration: [Confirm the appropriate selection above and disclose any related compensation or grant requests.]

NO

Do you have any financial, professional, or organizational conflict relevant to this application?

  • No

5. Public discussion

Forum post link: This application thread.

Questions or feedback requested from the community

We would especially welcome feedback from PEN contributors on whether there are additional implementation constraints or failure scenarios that should be included in the integration assessment.

We would also appreciate pointers to any existing PEN-specific Octant tests or previously funded work that overlaps with our proposed scope.

Our intention is to make the integration easier to evaluate, not to duplicate work already completed.


6. Applicant attestation

I confirm that the information in this application is accurate to the best of my knowledge; that I have disclosed relevant prior compensation and conflicts; and that I understand any award remains subject to the published process and DAO approval.

Name / handle: @CreativesOnchain

Hi there, thanks for the application!

We recommend deferring this proposal to Round 2 considering the demo already shows the main issue. Creating a topic within holders.vote in order to further engage with the PEN Community would also help to raise awareness.

Happy to add you to the TG group!