32 featdemo add buidl like erc 3643 demo asset#35
Merged
Conversation
Add a local Giwa MVP asset profile that keeps the ERC-3643 token generic while binding BUIDL-like regulatory behavior through Manifest, Recipe, and Element configuration. This creates a clean baseline before replacing assumptions with official BUIDL materials.\n\nConstraint: Official BlackRock/Securitize BUIDL code and compliance materials are not yet available.\nRejected: Hardcoding QP or transfer restrictions in a bespoke token override | It would obscure the product model where asset-specific rules are profile and Manifest configuration.\nConfidence: medium\nScope-risk: narrow\nDirective: Treat this as an assumption-based demo profile; revise against official BUIDL materials before claiming real BUIDL compatibility.\nTested: forge fmt --check src/demo/BuidlLikeDemoAsset.sol test/fixtures/TREXSuite.sol test/integration/IntegrationBase.sol test/integration/BUIDLLikeFlow.t.sol; forge test --offline --match-path 'test/integration/BUIDLLikeFlow.t.sol' -vv; forge test --offline; git diff --check\nNot-tested: Real BlackRock/Securitize BUIDL integration, issuer claim model, NAV, redemption, distribution, production identity/whitelist rails
Anchor the Giwa MVP profile assumptions in Manifest metadata and document how DS/Securitize-style compliance maps into the ERC-3643/T-REX fixture without claiming real BUIDL compatibility. Constraint: Real Securitize/BUIDL integration details are not implemented, so the profile must remain explicitly BUIDL-like and adapter-oriented. Rejected: Baking BUIDL-specific transfer logic into the token | would bypass the Manifest/Recipe/Element product model. Confidence: high Scope-risk: narrow Directive: Replace AI/QP test flags with ONCHAINID claim fixtures before treating this as production eligibility logic. Tested: forge fmt --check src/demo/BuidlLikeDemoAsset.sol test/integration/BUIDLLikeFlow.t.sol; forge test --offline --match-path test/integration/BUIDLLikeFlow.t.sol -vv; forge test --offline; git diff --check Not-tested: real Securitize/TA adapter, NAV/redemption/monthly distribution rails
Extend the local ERC-3643 test issuance profile with a BUIDL-like fund recipe that requires QP eligibility and a M-equivalent minimum trade amount, plus tests for below-minimum rejection. Constraint: This is still a BUIDL-like test issuance, not real BlackRock/Securitize integration. Rejected: Adding the minimum gate to the generic Fund3c7Recipe | would alter unrelated fund fixtures and conflate generic 3(c)(7) eligibility with this demo profile. Confidence: high Scope-risk: narrow Directive: Keep BUIDL-specific facts in profile-specific Recipe/Element bindings until a Manifest compiler supports asset-scoped facts natively. Tested: forge fmt --check src/compliance/elements/BuidlMinimumInvestment.sol src/compliance/recipes/BuidlLikeFundRecipe.sol src/demo/BuidlLikeDemoAsset.sol test/integration/IntegrationBase.sol test/integration/BUIDLLikeFlow.t.sol test/unit/compliance/BuidlLikeFundRecipe.t.sol; forge test --offline --match-path test/integration/BUIDLLikeFlow.t.sol -vv; forge test --offline --match-path test/unit/compliance/BuidlLikeFundRecipe.t.sol -vv; forge test --offline; git diff --check Not-tested: real Securitize/TA adapter, ONCHAINID-backed AI/QP claim expiry, NAV/redemption/monthly distribution rails
Make the BUIDL-like ERC-3643 demo use a test-only transfer-agent style source for investor facts before syncing them into the ERC-3643 registry and Corner Store Elements. Constraint: The demo needs to prove compliance validation and trade execution, not real BlackRock BUIDL or Securitize connectivity. Rejected: Calling AI/QP/sanctions Elements directly from BUIDL flow tests | hides the external eligibility-source boundary the MVP needs to demonstrate. Confidence: high Scope-risk: narrow Directive: Keep real TA/API/claim issuer connectivity out of this fixture; replace the sync seam only when production issuer requirements are known. Tested: forge fmt --check src/demo/BuidlLikeDemoAsset.sol test/fixtures/TREXSuite.sol test/fixtures/MockSecuritizeTA.sol test/integration/IntegrationBase.sol test/integration/BUIDLLikeFlow.t.sol src/compliance/elements/BuidlMinimumInvestment.sol src/compliance/recipes/BuidlLikeFundRecipe.sol test/unit/compliance/BuidlLikeFundRecipe.t.sol; forge test --offline --match-path test/integration/BUIDLLikeFlow.t.sol -vv; forge test --offline --match-path test/unit/compliance/BuidlLikeFundRecipe.t.sol -vv; forge test --offline; git diff --check Not-tested: real Securitize/TA API, production ONCHAINID AI/QP claim expiry/revocation, NAV/redemption/distribution rails
0xMuang
added a commit
that referenced
this pull request
Jul 14, 2026
Record the RFQ backend as a TypeScript SDK and local-reference path before MVP demo backend work begins, while preserving pending PR context for RFQ hardening, E2E, CLI, and BUIDL fixtures. Constraint: Open PRs #24, #28, #29, #30, and #35 already cover parts of RFQ hardening, protected-router scenarios, live demo, CLI, and BUIDL-like fixtures. Rejected: Treating an RFQ backend as a Corner Store-operated production server | would blur operator responsibilities for pricing, signer custody, inventory, hosting, and compliance prechecks. Confidence: high Scope-risk: narrow Directive: Implement RFQ SDK interfaces first; any MVP backend must reuse merged E2E/CLI/BUIDL paths instead of creating parallel demo infrastructure. Tested: git diff --check Not-tested: services/rfq implementation or runtime tests; documentation-only change
Resolve the BUIDL demo PR after main advanced with RFQ, compliance lifecycle, E2E, CLI, and RFQ SDK work. Constraint: BUIDL-like demo must use the current Manifest lifecycle and shared TREXCore fixture. Rejected: Reverting to the old TREXSuite deployment body | would duplicate TREXCore and break live-script fixture sharing. Confidence: high Scope-risk: moderate Directive: Keep real BlackRock BUIDL/Securitize/TA integration out of this fixture; use it only as a compliance validation demo profile. Tested: forge fmt --check BUIDL-related files; forge test --offline --match-path test/integration/BUIDLLikeFlow.t.sol -vv; forge test --offline --match-path test/unit/compliance/BuidlLikeFundRecipe.t.sol -vv; git diff --cached --check Not-tested: full scripts/check.sh for this merge reconciliation; rely on GitHub CI after push
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BUIDL-like ERC-3643 demo asset fixture를 추가했습니다.
이번 PR의 목적은 실제 BlackRock BUIDL/Securitize를 직접 연동하는 것이 아니라, BUIDL 같은 규제형 자산이 ERC-3643으로 발행되었다고 가정했을 때 Corner Store가 compliance를 검증하고 Router 경로에서 거래를 실행/차단할 수 있는지 테스트하는 것입니다.
What changed
BUIDL-like demo profile 추가
BUIDL-like ERC-3643 Demo AssetbBUIDLBUIDL-like fund recipe 추가
5,000,000unitsMock Securitize/TA fixture 추가
BUIDL-like integration test 추가
문서 업데이트
Verification
forge fmt --check src/demo/BuidlLikeDemoAsset.sol test/fixtures/TREXSuite.sol test/fixtures/MockSecuritizeTA.sol test/integration/IntegrationBase.sol test/integration/BUIDLLikeFlow.t.sol src/compliance/elements/BuidlMinimumInvestment.sol src/compliance/recipes/BuidlLikeFundRecipe.sol test/unit/compliance/BuidlLikeFundRecipe.t.solforge test --offline --match-path test/integration/BUIDLLikeFlow.t.sol -vvforge test --offline --match-path test/unit/compliance/BuidlLikeFundRecipe.t.sol -vvforge test --offlinegit diff --checkResult:
Out of scope