Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move Fast USDC into its own repo #10811

Open
turadg opened this issue Jan 7, 2025 · 0 comments
Open

move Fast USDC into its own repo #10811

turadg opened this issue Jan 7, 2025 · 0 comments
Assignees

Comments

@turadg
Copy link
Member

turadg commented Jan 7, 2025

What is the Problem Being Solved?

Fast USDC is not part of the Agoric SDK but was built in the agoric-sdk repo as a convenience. Other developers need to build things like Fast USDC without making changes to agoric-sdk, but that's very difficult.

Description of the Design

Pull the @agoric/fast-usdc package into its own repo.

For each of these integration test suites, developing tooling to run them outside agoric-sdk and then move the existing tests to the new repo to use them.

  • Bootstrap/RunUtils (boot/test/fast-usdc)
  • a3p-integration (proposals/f:fast-usdc)
  • multichain-testing (multichain-testing/test/fast-usdc/)

Evaluate moving some of the multichain-testing to bootstrap tests to verify it's the better DX. (context)

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

@turadg turadg added this to the FU5: Mainnet proposal milestone Jan 7, 2025
@turadg turadg self-assigned this Jan 27, 2025
@turadg turadg removed this from the FU5: Mainnet proposal milestone Jan 27, 2025
mergify bot added a commit that referenced this issue Feb 12, 2025
refs: #10811

## Description

While working on #10811 I got errors like,
```
  Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/opt/agoric/fast-usdc/node_modules/@agoric/orchestration/tools/ibc-mocks.ts' imported from /opt/agoric/fast-usdc/packages/fast-usdc/test/fixtures.ts
```

That's because the "tools" path was not in the package.json. This fixes that.

It also brings in some commits from #10480 to support fully using .ts in the new codebase.

### Security Considerations
none

### Scaling Considerations
none

### Documentation Considerations
none

### Testing Considerations
CI suffices

### Upgrade Considerations
no runtime changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant