Point Memo clients to the v4 program (Memo4c2p…) - #418
Conversation
This PR updates the Memo IDL and clients to target the v4 program at `Memo4c2pN8afCj432Lb7RMVKi9PbQnnW7ewFFaV3oAH`, replacing the v3 address (`MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr`). v4 is a `pinocchio`-based reimplementation that is wire-compatible with v3 (identical instruction layout and optional signers) but consumes roughly 95% fewer compute units. The repo's `program/` folder already builds v4; this change brings the client-facing address in line with it. The public API of every client is unchanged, only the program address they target.
joncinque
left a comment
joncinque
left a comment
There was a problem hiding this comment.
Yes! We might need to advertise this change to the users of the packages somehow, since memo v4 has a slightly different output format if I'm not mistaken.
People shouldn't rely on the log formatting, but who knows what's really happening in the wild.
|
I was thinking of doing a minor bump for |
It'll be safer to do a breaking release either way, so minor for the 0.x line, and major otherwise |
|
Seems like all JS and Rust clients are under 0.x versioning so I'll do minor bumps all round. |
2 participants
This PR updates the Memo IDL and clients to target the v4 program at
Memo4c2pN8afCj432Lb7RMVKi9PbQnnW7ewFFaV3oAH, replacing the v3 address (MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr).v4 is a
pinocchio-based reimplementation that is wire-compatible with v3 (identical instruction layout and optional signers) but consumes roughly 95% fewer compute units. The repo'sprogram/folder already builds v4; this change brings the client-facing address in line with it. The public API of every client is unchanged, only the program address they target.