GreenSmokeNetwork — GSN-514265 update, GSNAGENT-d8d495 collection, co…

[GreenSmokeCustoms-Ai]

…ntract labels

• tokens/GSN-514265: fix description typos (AI-Agents/DeAI), website → app.greensmoke.network, add team-vesting lockedAccounts, refreshed 200x200 logos
• tokens/GSNAGENT-d8d495 (NEW): MX-8004 soulbound agent-identity NFT collection issued by the GreenSmokeNetwork factory
• accounts: labels for Factory, Prediction Market v2, Identity Registry, Reputation Registry + shared greensmoke icon
• refresh X handle to @GreenSmokeNet on existing GreenSmokeNetwork entries

[GreenSmokeCustoms-Ai]

{
"message": "30363631376130303063386530656165623764353635323538653061333636356466633034396265",
"signature": "bafa00770d40f90b1089f2bd981629fd4349fcc1b5cd711ac003ca6a279a5225633ec337006448051925b8f79e45c5dda0d13cb21ab1de2dae0979b4211f1b08",
"address": "erd1c83tgujs47scafsu7kyt0myxeg50aw5lzxm47y73ue45ktzfkgjq8m3fae",
"version": 1,
"signer": "extension"
}

[paulmultiversx]

Hi, @GreenSmokeCustoms-Ai

We have a limitation at only 1 asset / PR so please split it in separate PRs.

Thanks

[GreenSmokeCustoms-Ai]

Split into one-asset PRs as requested: #4730 (GSN-514265 token), #4731 (GSNAGENT-d8d495 collection), #4732–#4736 (contract labels). Closing this bundled PR.

@paulmultiversx one thing needs your guidance: these assets are owned by our 2-of-3 xSafe multisig erd1qqqqqqqqqqqqqpgq7pceh6mvdtkfqwxdnsrcdnxzu22awhtrkgjqn2qtru (self-owned), so the check-signature bot resolves the required signer to the multisig SC address itself — which cannot produce an ed25519 message signature. Each split PR carries a commit-sha signature from our deployer/operator wallet erd1c83tgujs47scafsu7kyt0myxeg50aw5lzxm47y73ue45ktzfkgjq8m3fae (deployed all the contracts and owned the token before the multisig migration) as proof of control. Could you verify manually, or advise your preferred flow for multisig-owned assets?