Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / hypercerts-org/hypercerts issues and pull requests
#1099 - TASK: Define a set of strategies for hyperboard content rendering
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:docs
#1098 - FEAT: Blueprint registry form for address input
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend, category:offchain
#1097 - FEAT: Set default name, company name, and image for Hypercerts minters
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend
#1096 - FEAT: Blueprints of Hypercerts are used for speakers to send them their minting link
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:offchain
#1095 - TASK: Add “Create registry form”, allow for whitelisting organizer addresses
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend
#1094 - TASK: Add “Create Hypercert blueprint” form, allow organizers to create blueprints.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend
#1093 - TASK: Add list view for hypercert-blueprints for organizers
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend
#1092 - TASK: Add detail view for Hypercert-blueprints
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend
#1091 - TASK: Add delete Hypercert-blueprint functionality
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend, category:offchain
#1090 - FEAT: We should use Plasmic as a wrapper for our custom code components
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:offchain
#1089 - FEAT: Sponsorship will be a separate website and separate entity. It will provide a central place where you can do this.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 3 comments
Labels: category:frontend, category:ideas
#1088 - TASK: Set up a project in Plasmic.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:devops
#1087 - TASK: Set up a project for Vercel.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 3 comments
Labels: category:devops
#1086 - TASK: Decide on technology stack
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:ideas
#1085 - TASK: Add form to allow creating multiple related hypercert-blueprints
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend
#1084 - [SDK] Add 'image grabber' for building the hypercert SVGs
Issue -
State: closed - Opened by bitbeckers about 1 year ago
- 1 comment
#1083 - As a system, I want to use sign-in-with-Ethereum to permission access for users.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 7 comments
#1082 - [EVM] Deploy to Sepolia
Issue -
State: closed - Opened by bitbeckers about 1 year ago
Labels: category:devops
#1081 - EPIC: 9 - Hypercert marketplace
Issue -
State: closed - Opened by bitbeckers about 1 year ago
Labels: category:onchain
#1080 - EPIC: 8 - Contributor Consent and permissions management
Issue -
State: open - Opened by benedictvscriticus about 1 year ago
- 2 comments
#1079 - TASK: Create blueprint to Hypercerts form
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:frontend
#1078 - SPIKE: Research the possibilities of creating a hypercerts for a non-financial contributor without a wallet
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 2 comments
Labels: category:docs
#1077 - TASK: Define blueprint to mint flow for hypercerts owner checkout
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
Labels: category:docs
#1076 - STORY: As a hyperboard owner, I'm able to create a new hyperboard
Issue -
State: closed - Opened by bitbeckers about 1 year ago
Labels: category:onchain
#1075 - STORY: As a contributor, I want to be able to receive a prefilled link from FtC where I mint my Hypercerts.
Issue -
State: closed - Opened by Jipperism about 1 year ago
Labels: category:offchain
#1075 - STORY: As a contributor, I want to be able to receive a prefilled link from FtC where I mint my Hypercerts.
Issue -
State: open - Opened by Jipperism about 1 year ago
Labels: category:offchain
#1074 - STORY: As an organiser, I am able to send a prefilled link to the speaker for minting a hypercert for their talk.
Issue -
State: closed - Opened by Jipperism about 1 year ago
Labels: category:frontend, category:offchain
#1074 - STORY: As an organiser, I am able to send a prefilled link to the speaker for minting a hypercert for their talk.
Issue -
State: closed - Opened by Jipperism about 1 year ago
Labels: category:frontend, category:offchain
#1073 - EPIC: 6 - Retroactive funding of non-financial contributors
Issue -
State: open - Opened by Jipperism about 1 year ago
- 2 comments
Labels: category:ideas
#1073 - EPIC: 6 - Retroactive funding of non-financial contributors
Issue -
State: closed - Opened by Jipperism about 1 year ago
- 2 comments
Labels: category:ideas
#1072 - STORY: As a hyperboard owner, I want to be able to control the display size of hypercerts using a predefined set of strategies.
Issue -
State: open - Opened by Jipperism about 1 year ago
- 5 comments
Labels: category:frontend
#1072 - STORY: As a hyperboard owner, I want to be able to control the display size of hypercerts using a predefined set of strategies.
Issue -
State: closed - Opened by Jipperism about 1 year ago
- 5 comments
Labels: category:frontend
#1071 - EPIC: 7 - Hypercert within hyperboard display admin for owners
Issue -
State: open - Opened by Jipperism about 1 year ago
Labels: category:offchain
#1071 - EPIC: 7 - Hypercert within hyperboard display admin for owners
Issue -
State: closed - Opened by Jipperism about 1 year ago
- 1 comment
Labels: category:offchain
#1070 - EPIC: 5 - Hyperboard owner admin panel
Issue -
State: closed - Opened by Jipperism about 1 year ago
Labels: category:frontend, category:offchain
#1070 - EPIC: 5 - Hyperboard owner admin panel
Issue -
State: open - Opened by Jipperism about 1 year ago
Labels: category:frontend, category:offchain
#1069 - FEAT: As an owner, I want to be able to choose which logo is displayed on the Hypercert.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
#1069 - FEAT: As an owner, I want to be able to choose which logo is displayed on the Hypercert.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
#1068 - WIP: Hyperboard contract
Pull Request -
State: open - Opened by Abhimanyu121 about 1 year ago
- 1 comment
#1067 - Feat/accepted tokens
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1066 - Feat/accepted tokens
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1065 - feat(tokens): surface accepted tokens
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1065 - feat(tokens): surface accepted tokens
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1064 - 1053 sdk sdk and contract should build for cjs and esm
Pull Request -
State: open - Opened by bitbeckers about 1 year ago
#1064 - 1053 sdk sdk and contract should build for cjs and esm
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1064 - 1053 sdk sdk and contract should build for cjs and esm
Pull Request -
State: open - Opened by bitbeckers about 1 year ago
#1063 - nitial trader implementation
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
- 1 comment
#1062 - GR18 hypercert minting link generation scripts
Pull Request -
State: closed - Opened by ccerv1 about 1 year ago
#1061 - fix(graph): update mapping to claim
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1061 - fix(graph): update mapping to claim
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1060 - Fix/workspace label
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1059 - [dApp] Set up development/production release Plasmic
Issue -
State: closed - Opened by bitbeckers about 1 year ago
- 1 comment
Labels: category:frontend, p2:grabbag
#1058 - 1052 subgraph a claimed token should indicate whether it was claimed from an allowlist
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1057 - feat(db): update allowlist query
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1056 - [FE] Filter hidden hypercerts from supabase
Issue -
State: closed - Opened by bitbeckers about 1 year ago
#1055 - chore(turbo): split graph deploys
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1054 - [Graph] Refactor and expand tests
Issue -
State: closed - Opened by bitbeckers about 1 year ago
- 1 comment
Labels: category:offchain, p2:grabbag
#1053 - [SDK] SDK and contract should build for CJS and ESM
Issue -
State: closed - Opened by bitbeckers about 1 year ago
- 3 comments
#1052 - [Graph] A claimed token should indicate whether it was claimed from an allowlist
Issue -
State: open - Opened by ccerv1 about 1 year ago
- 12 comments
Labels: category:offchain
#1051 - Feat/batch burn
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1050 - [FE][Bug] pop-up and progress bar doesn't finish when using a multi-sig
Issue -
State: closed - Opened by holkexyz about 1 year ago
#1049 - Example app TS/JS
Issue -
State: closed - Opened by bitbeckers about 1 year ago
- 3 comments
Labels: category:docs, category:frontend, category:sdk
#1048 - chore(update): update deps graph and sdk
Pull Request -
State: closed - Opened by bitbeckers about 1 year ago
#1047 - Missing dependency: concat-stream
Issue -
State: closed - Opened by bitbeckers about 1 year ago
#1046 - Update README.md: fixed errors
Pull Request -
State: closed - Opened by Aryan9592 about 1 year ago
#1045 - feat: validation checks for github repos
Issue -
State: closed - Opened by ccerv1 about 1 year ago
#1044 - FEAT: Hypercerts represent work.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1043 - STORY: As a developer, I want to have architecture documentation available for hyperboard admin flows.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
Labels: category:docs
#1042 - STORY: As an organiser, I want to be able to create and manage a registry behind a hyperboard.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
Labels: category:offchain
#1041 - FEAT: FTC Hyperboards are integrated in a standalone website for the POC.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
Labels: category:devops
#1040 - STORY: As an organizer, I want to be able to define properties of Hypercerts in a registry behind a hyperboard.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
Labels: category:offchain
#1039 - STORY: As a super admin, I want to be able to define the size of hypercerts on a hyperboard.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
#1038 - TASK: Link hyperboard frontend with hypercert data
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1037 - TASK: Implement registry overview and check-out as designed by UI/UX designer
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 6 comments
Labels: category:frontend
#1036 - TASK: Create registry database and schema
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 2 comments
Labels: category:offchain
#1035 - TASK: Define and research a splitter contract for retroactive Hyperboard donations.
Issue -
State: open - Opened by benedictvscriticus about 1 year ago
- 2 comments
#1034 - TASK: Design Hyperboards for implementation using Chakra components or similar.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1033 - FEAT: One type of Hypercert is directly minted by an organization and is not eligible for retroactive funding.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1032 - FEAT: One type of Hypercerts is blueprint-based and is eligible for receiving an attestation of retroactive funding.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1031 - FEAT: One type of Hypercerts is directly minted by the organizer and is eligible for receiving an attestation of retroactive funding
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1030 - FEAT: One type of Hypercert is blueprint-based and is not eligible for retroactive funding.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1029 - TASK: Research best practices for the display of treemaps
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
#1028 - FEAT: When hypercerts are not yet minted, we refer to them as blueprint-hypercerts.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
#1027 - TASK: Define requirements for the ownership structure of Hyperboards
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
Labels: category:docs
#1026 - TASK: Design the Hyperboard display
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1025 - FEAT: A hyperboard is an overview of all entities that hold hypercerts to an event.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
#1024 - FEAT: The description of talks should show the speaker name, speaker and talk description.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 6 comments
Labels: category:frontend
#1023 - FEAT: Contribution categories are represented by different shapes and or colours.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
#1022 - TASK: Define an image review process for assessing appropriateness
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
Labels: category:docs
#1021 - TASK: Research and define requirements for images on Hyperboards according to the following variables
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1020 - FEAT: Funded hypercerts are displayed with the owner metadata, i.e. logo, name, type of contribution, and talk description
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1019 - As a contributor, I want to be able to see my Hypercert on the Hyperboard that shows my contributions and my details.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1018 - STORY: As an organiser, I want to be able to define the splitter metrics for the distribution of retroactive funding to a Hyperboard across categories.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1017 - As a funder, I want to be able to see my Hypercert on the Hyperboard for the cause I supported.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1016 - STORY: As an organiser, I want to be able to include a Hypercert in a Hyperboard.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment
Labels: category:frontend, category:offchain
#1015 - TASK: create data structure for blueprints of Hypercerts that can be created by a super admin
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1014 - TASK: build registry for Blueprint HCs on the backend
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1013 - DEF: The superadmin can create a hyperboard as a collection of hypercerts and other hyperboards (elements of a hyperboard) (i.e. hyperboards are composable).
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1012 - FEAT: Super admin can create Hyperboard.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
#1011 - STORY: As a hyperboard owner, I want to be able to control the display size of hypercerts using a predefined set of strategies.
Issue -
State: closed - Opened by benedictvscriticus about 1 year ago
- 1 comment