chainId
need to add chainId to admin invite message. and check it onchain
otherwise admin payload can be used in other chain with same contract address
was
:::
should be
::::
deadline
should add some deadline timestamp after which invite will be expired
personalizing
admin should can to create invite personal to user. otherwise "bad user" can request another one invite, and use unnecessary for other user
In total:
all this should be optional. Our contract should understand all formats.
For example, the admin message can be like this:
<some string data>:<typeof message>:<address of communityContract>:<array of rolenames (sep=',')>:<optional chainid>:<optional deadline>:<optional recipient>:<some string data>
chainId need to add chainId to admin invite message. and check it onchain otherwise admin payload can be used in other chain with same contract address was
deadline should add some deadline timestamp after which invite will be expired
personalizing admin should can to create invite personal to user. otherwise "bad user" can request another one invite, and use unnecessary for other user
In total: all this should be optional. Our contract should understand all formats. For example, the admin message can be like this: