Skip to content

Conversation

@mariocynicys
Copy link
Collaborator

Wanted to flag it as an issue but looks like we can't have issues in forked repo.
So leaving it as an inline todo for now.

@mariocynicys
Copy link
Collaborator Author

oops we can actually have issues in this repo: https://stackoverflow.com/questions/16406180/is-there-a-way-to-add-issues-to-a-github-forked-repo-without-modifying-the-orig

@borngraced @shamardy
could u enable issues here pls :)

@borngraced
Copy link
Collaborator

oops we can actually have issues in this repo: https://stackoverflow.com/questions/16406180/is-there-a-way-to-add-issues-to-a-github-forked-repo-without-modifying-the-orig

@borngraced @shamardy could u enable issues here pls :)

done

Comment on lines +40 to +41
// TODO: There doesn't seem to be a sessionProperties field as per the spec: https://specs.walletconnect.com/2.0/specs/clients/sign/rpc-methods#wc_sessionsettle
// Instead, there is an optional specialNamespaces field that's missing.
Copy link
Collaborator

@borngraced borngraced Jun 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some implementations uses it like keplr WalletConnect

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but why isn't such a field in the spec??
i found a field with the same name somewhere else but it already has a completely different data/structure.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmmm...session_properties takes an arbitrary value, so it's unto you to know what the wallet you're targeting includes in theirs

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.

3 participants