marigold-dev / marigold-dev/tzsafe-inside
Save safes created from TzSafe dApp in database
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
From Slack:
> In case Umami reuses your smart contracts (not the case at the moment), we probably want to register the list of safes originated from TzSafe somewhere (e.g. SQL) for later potential use, e.g. airdrops. We wouldn't want to accidentally airdrop a safe that has been created from Umami only.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the TzSafe and Umami safe-creation flows and the existing database or persistence layer, then determine how origin is represented. Done means safes created from TzSafe are recorded separately from Umami-only safes and remain available for later use such as airdrops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql, typescript
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100