Skip to content
This repository has been archived by the owner on Feb 11, 2023. It is now read-only.

Handling Enums for transfer restrictions #20

Open
bitbeckers opened this issue Jan 19, 2023 · 3 comments
Open

Handling Enums for transfer restrictions #20

bitbeckers opened this issue Jan 19, 2023 · 3 comments
Assignees
@ryscheng @Jipperism @bitbeckers
Labels
enhancement New feature or request
Milestone
v0.2

Comments

@bitbeckers
Copy link
Collaborator

Currently we don't expose the Transfer restrictions in the SDK.

  • Enums are expected as BigNumber input
  • Enums are not exposed via the ABI
  • We use enums to define transfer restriction so we should make handling these reasonably foolproof
@bitbeckers bitbeckers added this to the v0.2 milestone Jan 19, 2023
@bitbeckers bitbeckers mentioned this issue Jan 20, 2023
Merged
@Jipperism
Copy link
Collaborator

@bitbeckers would you agree this is finished?

@bitbeckers
Copy link
Collaborator Author

@Jipperism is there a definition available in the SDK? For instance a mapping from String to BigNumber?

@Jipperism
Copy link
Collaborator

@bitbeckers it lives in the frontend. Probably nice to add it to the SDK so it's clear for others as well.

@bitbeckers bitbeckers mentioned this issue Jan 31, 2023
Closed
@bitbeckers bitbeckers added the enhancement New feature or request label Jan 31, 2023
@ryscheng ryscheng mentioned this issue Feb 11, 2023
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ryscheng ryscheng

@Jipperism Jipperism

@bitbeckers bitbeckers

Labels
enhancement New feature or request
Projects
hypercerts-v0.2
Status: Todo
Milestone
v0.2
Development

No branches or pull requests
3 participants
@ryscheng @Jipperism @bitbeckers