# RSKIP-694: Network Upgrade Cardamom

**URL:** <https://research.rsk.dev/t/rskip-694-network-upgrade-cardamom/552>\
**Category:** RSKIP\
**Created:** [October 7, 2026, 6:40pm UTC](https://research.rsk.dev/t/rskip-694-network-upgrade-cardamom/552 "2026-10-07T18:40:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![adrian.eidelman](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@adrian.eidelman](https://research.rsk.dev/u/adrian.eidelman)\
**Post date:** [October 7, 2026, 6:40pm UTC](https://research.rsk.dev/t/rskip-694-network-upgrade-cardamom/552/1 "2026-10-07T18:40:12Z")

</div>

Hello to the Rootstock community!

A new network upgrade proposal has been published and is now open for discussion.

The [Cardamom network upgrade proposal](https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP694.md) introduces several consensus protocol improvements, including changes to transaction formats, Account Abstraction support, and enhancements to the PowPeg pegout process.

Here are the key improvements proposed for inclusion in the Cardamom upgrade:

**RSKIP-378: Enforce release transaction size limit**

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP378.md>

**RSKIP-455: PowPeg migration to multiple outputs**

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP455.md>

**RSKIP-543: Typed Transaction Envelope**

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP543.md>

**RSKIP-545: Set Code for EOAs**

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP545.md>

**RSKIP-546: Implement EVM’s Type 1 and Type 2 Envelope formats**

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP546.md>

**RSKIP-559: Deterministic selection of the next pegout to confirm**

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP559.md>

**RSKIP-643: New pegout registration method**

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP643.md>

**RSKIP-692: Direct precompile call failure semantics**

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP692.md>

We warmly invite the Rootstock community to review the proposal, participate in the discussion, share feedback, and suggest improvements.

Your feedback is an important part of the process of shaping the future of the Rootstock protocol.

Thank you for your continued support and engagement!

---

<div class="post-metadata">

**Author:** ![GoldenGatsby](https://yyz2.discourse-cdn.com/flex036/user_avatar/research.rsk.dev/goldengatsby/32/196_2.png) [@GoldenGatsby](https://research.rsk.dev/u/GoldenGatsby)\
**Post date:** [October 7, 2026, 6:57pm UTC](https://research.rsk.dev/t/rskip-694-network-upgrade-cardamom/552/2 "2026-10-07T18:57:54Z")

</div>

Looking really strong. Account abstraction is a great feature to include and already heard positive comments about multiple utxos in peg-outs.

---

<div class="post-metadata">

**Author:** ![shreemoy](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@shreemoy](https://research.rsk.dev/u/shreemoy)\
**Post date:** [October 7, 2026, 8:30pm UTC](https://research.rsk.dev/t/rskip-694-network-upgrade-cardamom/552/3 "2026-10-07T20:30:12Z")

</div>

Excited to see this ! I am one of the coauthors of the proposals related to account abstraction. I am grateful that they are being considered for inclusion in this network upgrade. RSKIP-545 is based on EIP-7702, which has seen strong adoption on ethereum. If accepted by the rootstock community, developers will be able to use all the existent tooling for account abstraction for evm compatible chains

---

<div class="post-metadata">

**Author:** ![adrian.eidelman](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@adrian.eidelman](https://research.rsk.dev/u/adrian.eidelman)\
**Post date:** [October 8, 2026, 1:26pm UTC](https://research.rsk.dev/t/rskip-694-network-upgrade-cardamom/552/4 "2026-10-08T13:26:02Z")

</div>

We’ve also included RSKIP-378: Enforce release transaction size limit as part of the list of proposed RSKIPs