Feature - Show current hDAO curation amount

.dev

@@ -0,0 +1,7 @@
+REACT_APP_IPFS_KEY=''
+
+REACT_APP_BLOCKLIST_OBJKT='https://raw.githubusercontent.com/hicetnunc2000/hicetnunc/main/filters/o.json'
+REACT_APP_BLOCKLIST_WALLET='https://raw.githubusercontent.com/hicetnunc2000/hicetnunc/main/filters/w.json'
+REACT_APP_BLOCKLIST_BAN='https://raw.githubusercontent.com/hicetnunc2000/hicetnunc/main/filters/b.json'
+
+REACT_APP_GRAPHQL_API='https://hdapi.teztools.io/v1/graphql'

.env

@@ -1,21 +1,8 @@
-REACT_APP_UNGRUND_POST_IPFS='http://0.0.0.0:5001/ipfs/post_json'
-REACT_APP_UNGRUND_POST_FILE2='http://13.59.82.99:5000/ipfs/post_file'
-REACT_APP_UNGRUND_ORIGINATE='http://0.0.0.0:3001/api/v1/mfp/originate'
-REACT_APP_UNGRUND_CONTRIBUTE='http://0.0.0.0:3001/api/v1/mfp/contribute'
-REACT_APP_UNGRUND_WITHDRAW='http://0.0.0.0:3001/api/v1/mfp/withdraw'
-REACT_APP_UNGRUND_TRANSFER=''
-REACT_APP_UNGRUND_FEED='http://0.0.0.0:5000/mfp/feed'
-REACT_APP_UNGRUND_TZ='http://0.0.0.0:5000/mfp/ledger'
-REACT_APP_UNGRUND_KT='http://0.0.0.0:5000/mfp/kt'
-REACT_APP_UNGRUND_INJECT='http://localhost:5000/auth/inject'
-REACT_APP_UNGRUND_POST_FILE='http://0.0.0.0:5001/ipfs/post_file'
-REACT_APP_UNGRUND_MINT='http://0.0.0.0:3001/api/v1/objkt/mint'
-REACT_APP_UNGRUND_CURATE='http://0.0.0.0:3001/api/v1/objkt/curate'
-REACT_APP_UNGRUND_COLLECT='http://0.0.0.0:3001/api/v1/objkt/collect'
-REACT_APP_UNGRUND_OBJKT_FEED='http://0.0.0.0:5000/objkt/feed'
-REACT_APP_UNGRUND_OBJKT_SWAPS='http://0.0.0.0:5000/objkt/swaps'
-REACT_APP_UNGRUND_OBJKT_ID='http://0.0.0.0:5000/objkt/id'
-REACT_APP_UNGRUND_OBJKT_TZ_LEDGER='http://0.0.0.0:5000/objkt/tz_ledger'
-REACT_APP_UNGRUND_OBJKT_TZ_SWAPS='http://0.0.0.0:5000/objkt/tz_swaps'
-REACT_APP_UNGRUND_OBJKT_SWAPS_METADATA='http://0.0.0.0:5000/objkt/swap_metadata'
-REACT_APP_UNGRUND_OBJKT_LEDGER='http://0.0.0.0:5000/objkt/ledger'
+REACT_APP_IPFS_KEY='eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJkaWQ6ZXRocjoweEY1NDdDNUIyMjMzMTc3MDZkZDdkODNEMjA4ODRkRDgxOTIxNTBiNEUiLCJpc3MiOiJuZnQtc3RvcmFnZSIsImlhdCI6MTYzMTA1NTgyNTAxMCwibmFtZSI6ImRldiJ9.Uw_dgYXOAA1znTrdXlOlXFYWh9U_pjg4QOl7nrt16SA'
+
+REACT_APP_BLOCKLIST_OBJKT='https://raw.githubusercontent.com/hicetnunc2000/hicetnunc-reports/main/filters/o.json'
+REACT_APP_BLOCKLIST_WALLET='https://raw.githubusercontent.com/hicetnunc2000/hicetnunc-reports/main/filters/w.json'
+REACT_APP_BLOCKLIST_BAN='https://raw.githubusercontent.com/hicetnunc2000/hicetnunc-reports/main/filters/b.json'
+
+REACT_APP_GRAPHQL_API='https://hdapi.teztools.io/v1/graphql'
+#REACT_APP_GRAPHQL_API='https://api.hicdex.com/v1/graphql'

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,65 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+If you need help with minting or managing assets, we ask to please wait at least 24 hours for issues to clear up. 
+
+Here are some useful tools that you can use to troubleshoot without us in the meantime:
+
+*See transaction history for an objkt*
+https://hicdex.com/objkt
+
+*See transaction history for your wallet address*
+https://hicdex.com/sold
+
+Please note that the discord is usually the best place to get the fastest support as there are mostly likely others experiencing the same issues as you and active HEN team members assisting with troubleshooting. Please seek help in the #help channel, and read recent dev updates in #dev-announcements. You can join the discord here: https://discord.gg/HhSYY7q5A8 
+
+-----------------------------------------------
+*Please fill out the following Bug Report Template
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**If you need help with minting or managing assets, please give us the following information**
+- your profile link
+- any other profile links affected
+- tezos wallet address
+- objkt #'s that are being affected
+
+**Screenshots**
+- screenshots of your minting process
+- screenshots of profiles affected
+- screenshots of the browser console (in chrome windows, press ctrl + shift + j to open the developer console)
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.
+Please include the wallet address (tz...) and/or the OBJKT number.

.github/ISSUE_TEMPLATE/faq_update.md

@@ -0,0 +1,34 @@
+---
+name: FAQ update
+about: Submit an update to the Hic et Nunc FAQs
+title: 'FAQ: [summary of change]'
+labels: FAQ
+assignees: violetforest
+
+---
+
+**Summary of change to FAQs you wish to make:**
+* For example: new page `foo.md`, edit to page `bar.md`. 
+* If want to reorder any existing page, note this here too.
+
+[*enter change here*]
+
+
+**If it's a new page, which navigation heading does it come under**
+* For example: Minting guide, FAQs, Misc
+
+[*enter navigation change here*]
+
+
+**Text change**
+* Add here the new text (and old text it's replacing if applicable)
+
+[*add new and/or replaced text here*]
+
+
+**Markdown**
+* If you've written the update using Markdown, replace the `FAQ in markfown format` below with your markdown-tagged text
+
+```Markdown
+Add FAQ text in Markfown format
+```

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: feature-request
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/dependabot.yml

@@ -0,0 +1,34 @@
+version: 2
+updates:
+- package-ecosystem: npm
+  directory: "/"
+  schedule:
+    interval: daily
+    time: "08:00"
+  open-pull-requests-limit: 10
+  ignore:
+  - dependency-name: fflate
+    versions:
+    - 0.6.10
+  - dependency-name: "@taquito/taquito"
+    versions:
+    - 8.0.6-beta.0
+    - 8.1.1
+    - 9.0.0
+  - dependency-name: "@taquito/beacon-wallet"
+    versions:
+    - 8.0.6-beta.0
+    - 9.0.0
+  - dependency-name: framer-motion
+    versions:
+    - 3.10.3
+    - 4.1.10
+    - 4.1.5
+    - 4.1.6
+    - 4.1.9
+  - dependency-name: "@testing-library/user-event"
+    versions:
+    - 13.0.13
+  - dependency-name: "@airgap/beacon-sdk"
+    versions:
+    - 2.2.3

.gitignore

@@ -2,17 +2,21 @@
 
 # dependencies
 /node_modules
+# IDEs
+.vscode
 
 # production
 /build
 /amplify
 # misc
-.env_prod
+#.env_prod
 
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
 
+.DS_Store
+
 # Elastic Beanstalk Files
 .elasticbeanstalk/*
 !.elasticbeanstalk/*.cfg.yml
@@ -33,3 +37,12 @@ amplifyconfiguration.json
 amplify-build-config.json
 amplify-gradle-config.json
 amplifytools.xcconfig
+
+# templates
+templates/html-image-scale/package-lock.json
+templates/html-image-scale/node_modules
+templates/html-image-scale/dist
+templates/html-image-scale/.parcel-cache
+
+# contributor specific (local) folders
+.next

.prettierrc

@@ -0,0 +1,6 @@
+{
+  "semi": false,
+  "singleQuote": true,
+  "tabWidth": 2,
+  "useTabs": false
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,90 @@
+# Citizen Code of Conduct
+
+## 1. Purpose
+
+A primary goal of Hicetnunc is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
+
+This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+We invite all those who participate in Hicetnunc to help us create safe and positive experiences for everyone.
+
+## 2. Open [Source/Culture/Tech] Citizenship
+
+A supplemental goal of this Code of Conduct is to increase open [source/culture/tech] citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
+
+Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
+
+If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
+
+## 3. Expected Behavior
+
+The following behaviors are expected and requested of all community members:
+
+- Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+- Exercise consideration and respect in your speech and actions.
+- Attempt collaboration before conflict.
+- Refrain from demeaning, discriminatory, or harassing behavior and speech.
+- Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+- Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+
+## 4. Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+- Violence, threats of violence or violent language directed against another person.
+- Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+- Posting or displaying sexually explicit or violent material.
+- Posting or threatening to post other people's personally identifying information ("doxing").
+- Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+- Inappropriate photography or recording.
+- Inappropriate physical contact. You should have someone's consent before touching them.
+- Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+- Deliberate intimidation, stalking or following (online or in person).
+- Advocating for, or encouraging, any of the above behavior.
+- Sustained disruption of community events, including talks and presentations.
+
+## 5. Weapons Policy
+
+No weapons will be allowed at Hicetnunc events, community spaces, or in other spaces covered by the scope of this Code of Conduct. Weapons include but are not limited to guns, explosives (including fireworks), and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. Community members are further expected to comply with all state and local laws on this matter.
+
+## 6. Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).
+
+## 7. Reporting Guidelines
+
+If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. [email protected].
+
+Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
+
+## 8. Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify hicetnunc2000 with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
+
+## 9. Scope
+
+We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues--online and in-person--as well as in all one-on-one communications pertaining to community business.
+
+This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
+
+## 10. Contact info
+
+[email protected]
+
+## 11. License and attribution
+
+The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).
+
+Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).
+
+_Revision 2.3. Posted 6 March 2017._
+
+_Revision 2.2. Posted 4 February 2016._
+
+_Revision 2.1. Posted 23 June 2014._
+
+_Revision 2.0, adopted by the [Stumptown Syndicate](http://stumptownsyndicate.org) board on 10 January 2013. Posted 17 March 2013._

CONTRIBUTING.md

@@ -0,0 +1,36 @@
+# CONTRIBUTING
+
+## PR
+
+We take PRs on a case-by-case basis. Please contact us in the discord in the #dev channel to have your PR considered.
+
+You will need to create a feature branch from the `main` branch, write all your code there, and then when you submit your PR you submit it against the `main` branch.
+
+If anything else is new to you, don't feel intimidated, come and join us on Discord and we'll take the time to help.
+
+## Components
+
+When creating a component you need to provide a few properties in order to render the component properly. Try to avoid creating prop drilling, or even accessing react context in a component. The components should be as dumb as possible. The only place where you should have access to API requests, or React.Context is at the page level (`src/pages/*`).
+
+In terms of standard its a good practice to first do global imports, then relative imports and finally scss imports. So a component would look something like this:
+
+```jsx
+import React from 'react' // a global import
+import { Button } from '../button' // a relative import
+import styles from './styles.module.scss' // a sass import
+
+export const MyComponent = () => {
+  return <div className={styles.container}>My Component</div>
+}
+```
+
+There are some auxiliary components that aren't doing much besides aiding with the layout. A good example of that is the `/src/pages/objkt-display` where you have `<Container/>` and `<Padding />`. These components are similar to what `reactstrap` provides, but we're trying to minimize our bundle size, so we're reducing on dependencies.
+
+## Learning Resources
+[Hicdex: the Hic Et Nunc indexer](https://leonnicholls.medium.com/hicdex-the-hic-et-nunc-indexer-bd45f27a228f)
+
+[Hic Et Nunc Metadata](https://leonnicholls.medium.com/hic-et-nunc-metadata-40e594530e31)
+
+[Minters for Hic Et Nunc](https://leonnicholls.medium.com/minters-for-hic-et-nunc-8b244b3d7ce0?source=user_profile---------1----------------------------)
+
+[Hic Et Nunc Smart Contracts (Part 1)](https://leonnicholls.medium.com/hic-et-nunc-smart-contracts-part-1-e4ad5d0934b9)