Skip to content

Feat/add 0g support p3 1 - #9760

Merged
maxime-oe merged 7 commits into
mainfrom
feat/add-0g-support-p3_1
Aug 5, 2026
Merged

Feat/add 0g support p3 1#9760
maxime-oe merged 7 commits into
mainfrom
feat/add-0g-support-p3_1

Conversation

@maxime-oe

@maxime-oe maxime-oe commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Explanation

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Low Risk
Additive chain registry entries only; no changes to auth, security, or shared controller logic.

Overview
Adds 0G mainnet (chain ID 16661 / 0x4115) to @metamask/assets-controllers so balances and pricing work when that network is enabled.

multicall.ts maps 0x4115 to the standard Multicall3 deploy (0xcA11…CA11), enabling batched on-chain reads on 0G. codefi-v2.ts maps the same chain ID to eip155:16661/slip44:1111116661 so Codefi can resolve native 0G token prices. The package changelog records the addition.

Reviewed by Cursor Bugbot for commit 2bde9fb. Bugbot is set up for automated code reviews on this repo. Configure here.

Adds 0G to the two Multicall3 contract-address maps
(assets-controllers/src/multicall.ts and assets-controller's
MulticallClient.ts), using the canonical mds1/multicall3 deployment
(0xcA11bde05977b3631167028862bE2a173976CA11) -- live-verified this
session against the primary RPC and both fallbacks, byte-identical
bytecode across all three, unlike Somnia which needed a non-canonical
chain-specific deployment.

Adds 0G to SPOT_PRICES_SUPPORT_INFO in codefi-v2.ts with its dedicated
slip44:1111116661 identifier (no real SLIP-44 registry entry, not
ETH-native, so not slip44:60) -- matching chain-input.yaml's Phase 0
native-asset convention.

Changelog PR links use a PR_NUMBER placeholder -- fill in with the
real PR number once opened.

Base network enablement (0G p3_1 -- core's price + multicall wiring,
one Base-enablement PR per the skill's core exception).
PR #9760 is now open; replace the PR_NUMBER placeholder with the real
number/link, matching the Arc/Somnia precedent (commits b204ff4,
51d85df).
assets-controller (singular) changes are not required and are not
expected to ever be required for a plain Base enablement's Multicall
wiring -- only assets-controllers (plural)'s multicall.ts matters.
Base network enablement skill updated accordingly.
# Conflicts:
#	packages/assets-controllers/CHANGELOG.md
# Conflicts:
#	packages/assets-controllers/CHANGELOG.md
@maxime-oe
maxime-oe added this pull request to the merge queue Aug 5, 2026
Merged via the queue into main with commit 74ba1fd Aug 5, 2026
62 checks passed
@maxime-oe
maxime-oe deleted the feat/add-0g-support-p3_1 branch August 5, 2026 12:32
@maxime-oe maxime-oe mentioned this pull request Aug 5, 2026
4 tasks
pull Bot pushed a commit to Reality2byte/core that referenced this pull request Aug 5, 2026
## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## [111.1.0]

### Added

- Add `offhours` field to `TokenRwaData` and `RwaTokenData` types to
support off-hours RWA trading windows
([MetaMask#9792](MetaMask#9792))
- `offhours.nextOpen`: ISO-8601 datetime when the next off-hours window
opens
- `offhours.nextClose`: ISO-8601 datetime when the next off-hours window
closes
- Field is only present when the asset's source reports off-hours
tradability; absence means off-hours trading is not supported
- Add 0G (`16661`/`0x4115`) entries in `multicall.ts` and `codefi-v2.ts`
([MetaMask#9760](MetaMask#9760))

### Changed

- Bump `@metamask/account-tree-controller` from `^7.6.0` to `^7.6.1`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/accounts-controller` from `^39.0.6` to `^39.0.7`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/keyring-controller` from `^27.1.0` to `^27.1.1`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/multichain-account-service` from `^13.0.0` to
`^13.0.1` ([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/network-enablement-controller` from `^6.0.2` to
`^6.0.3` ([MetaMask#9791](MetaMask#9791))

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Version and dependency-only changes with no runtime code in this diff;
risk is limited to consumers picking up the new assets-controllers minor
release.
> 
> **Overview**
> **Monorepo release `1180.0.0`** bumps the root
`@metamask/core-monorepo` version and cuts
**`@metamask/assets-controllers` `111.1.0`**, with changelog entries
moved from `[Unreleased]` into the new `111.1.0` section (RWA `offhours`
on `TokenRwaData` / `RwaTokenData`, 0G chain in `multicall.ts` /
`codefi-v2.ts`, plus prior dependency bumps).
> 
> **Downstream packages** now depend on `@metamask/assets-controllers`
**`^111.1.0`** instead of `^111.0.0`: `@metamask/assets-controller`,
`@metamask/bridge-controller`, and
`@metamask/transaction-pay-controller`, with matching changelog notes
and **`yarn.lock`** updates.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
e4fffd7. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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

Successfully merging this pull request may close these issues.

2 participants