Skip to content

Conversation

@IVSOP
Copy link

@IVSOP IVSOP commented Oct 29, 2025

Adds feature described in #391, allowing changing ownership of a core NFT and authority of a core collection, through the new surfnet_stealCore endpoint.

Example request, stealing this random core NFT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "surfnet_stealCore",
  "params": [
    "2mNhQ5GHcn2y4CtR32LSKvhNzRumeVH1PMkFdACwqtNz",
    "<key of the new owner>"
  ]
}

@MicaiahReid
Copy link
Member

Thanks for the PR, @IVSOP! This helps me understand the feature better.

Thoughts @lgalabru and @IVSOP on this PR as-is vs two cheatcodes:

This would make each endpoint more "full-featured", like surfnet_setAccount/surfnet_setTokenAccount

@IVSOP
Copy link
Author

IVSOP commented Oct 29, 2025

I didn't split the endpoint because the logic is the exact same (just write a key into data[1..33]). If you want to set the full data, then I think having two separate cheatcodes would be cleaner. as the arguments and logic would be slightly different.
In the future, if you want to also change the plugin information, then it would make even more sense to split into two cheatcodes, so this is future proofing as well

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