The “Punk Armada Stake API” is an advanced decentralized governance platform designed to facilitate the active participation of members in the PUNK Armada DAO. The platform integrates sophisticated web technologies with blockchain innovations in order to provide a robust environment for managing governance through proposals and for controlling digital assets in the form of NFTs. From core developer 1devndogs – “The PUNK Armada DAO is a unique concept and it has been super interesting to develop a new voting model for a DAO using soft staking of NFTs.”

Table Of Contents

I. The Basics Of The PUNK Armada DAO

• Part 1 – The PUNK Armada DAO NFT-Based Voting System
• Part 2 – The PUNK Armada DAO Penalty System 
• Part 3 – The PUNK Armada DAO Authentication Process
• Part 4 – The PUNK Armada DAO Technology Stack

III. PUNK Armada DAO DAPP Frontend Documentation

• Part 1 – Initial Screen – PUNK Armada DAPP Launched & Database Initialized
• Part 2 – PUNK Armada DAO Login Process With MetaMask
• Part 3 – Logged In Screen – PUNK Armada NFT Display & DAO Members List
• Part 4 – The Proposals List – Open & Closed PUNK Armada DAO Proposals
• Part 5 – The PUNK Armada DAO Voting Process – Options, Model & Actions
• Part 6 – Admin Only – Creating & Submitting PUNK Armada DAO Proposals

III. PUNK Armada DAO DAPP Backend Documentation

• Part 1 – PUNK Armada DAO Account Creation
• Part 2 – PUNK Armada DAO Authentication
• Part 3 – Fetching PUNK Armada DAO Proposal List 
• Part 4 – Fetching User’s PUNK Armada NFTs 
• Part 5 – Fetching PUNK Armada DAO Members 
• Part 6 – PUNK Armada DAO Proposal Creation
• Part 7 – Cron Job for PUNK Armada DAO Proposal Closure

I. The Basics Of The PUNK Armada DAO

– Part 1 – The PUNK Armada DAO NFT-Based Voting System

– Part 2 – The PUNK Armada DAO Penalty System 

– Part 3 – The PUNK Armada DAO Authentication Process

– Part 4 – The PUNK Armada DAO Technology Stack

Part 1 – The PUNK Armada DAO NFT-Based Voting System

– PUNK Armada DAO Introduction

– Real-time Validation Of PUNK Armada NFTs

– Soft Staking Of PUNK Armada NFTs

– PUNK Armada NFT Submission Process 

– PUNK Armada NFT Voting Impact 

PUNK Armada DAO Introduction – The PUNK Armada NFT serves as the governance token of the PUNK Armada DAO, and each PUNK Armada NFT owned by a member yields additional voting power – the more PUNK Armada NFTs a member has, the stronger his/her vote becomes. See a screenshot below of the NFT Voting System

Real-time Validation Of PUNK Armada NFTs – Real-time validation checks ensure voting compliance and maintain the integrity and fairness of the voting process. These validation checks are performed to ensure that PUNK Armada NFTs are not listed for sale (including on Blur, OpenSea, and Magic Eden) at the moment of voting and at the closing of the vote – that only active, non-listed PUNK Armada NFTs contribute to a member’s voting impact

By default a voting period lasts seven days, but Punk 4762 can manually change voting periods when creating proposals

From core developer 1devndogs – “Our backend will verify through each marketplace’s API that the PUNK Armada NFTs used for voting are not currently listed. For instance, if a user owns 100 NFTs, they could potentially list 50 and still use the unlisted 50 for voting purposes. It’s crucial that the NFTs used for voting remain unlisted and un-transferred throughout the duration of the proposal. At the moment of voting and the end of the voting period, we will conduct a verification of all votes and the status of the involved NFTs”

Soft Staking Of PUNK Armada NFTs – Soft staking, also known as “liquid staking”, allows PUNK Armada DAO members to prove ownership of PUNK Armada NFTs without locking them from potential appreciation or trade and is required in order to participate in DAO governance. In short, this model facilitates active DAO participation without members having to sacrifice asset liquidity

From core developer 1devndogs – “The UI development for the platform will clearly inform users about the voting rules through “soft staking,” ensuring transparency and community acceptance. Upon registering with the DAO and engaging in voting, users will be prompted to agree to these terms and conditions”

PUNK Armada NFT Submission Process – When voting, members select which of their PUNK Armada NFTs to use for voting. Only unlisted NFTs are considered valid for the vote

PUNK Armada NFT Voting Impact – The impact of a member’s vote is determined by the number of PUNK Armada NFTs used in the vote. For example, voting with 5 NFTs yields a voting power of 5. Additionally, it is possible for the same PUNK Armada NFT to be utilized in voting on multiple proposals, provided all guidelines are strictly adhered to

Part 2 – The PUNK Armada DAO Penalty System 

– PUNK Armada DAO Penalty System Introduction 

– What Is Considered “Bad Behavior” In The PUNK Armada DAO?

– What Are The Penalties For “Bad Behavior” In The PUNK Armada DAO?

PUNK Armada DAO Penalty System Introduction – The penalty system of the PUNK Armada DAO is designed to maintain order and fairness, and to support loyalty and community sentiment. As such, smart contracts automatically enforce rules and penalties if predefined conditions are violated. All penalties are recorded on the blockchain, providing a transparent record of why and how penalties were imposed.

From core developer 1devndogs – “The smart contracts utilized in the PUNK Armada DAO will show us that a transfer was made and the reservoir API if they are listed on an exchange. And this is what reveals a penalty, so it is stored in the blockchain.”

What Is Considered “Bad Behavior” In The PUNK Armada DAO? – There are currently only two “bad behaviors” that the PUNK Armada DAO platform considers as predefined conditions for the application of swift justice:

– Bad Behavior #1 – Voting with an NFT and then later listing it at some point during the voting period. Members who vote with a PUNK Armada NFT and later list it during the voting period will face penalties for misuse

– Bad Behavior #2 – Voting with an NFT and then later transferring it at some point during the voting period. Members who vote with a PUNK Armada NFT and later transfer it during the voting period will face penalties for misuse

What Are The Penalties For “Bad Behavior” In The PUNK Armada DAO? – Penalties for misuse are as follows and can be seen in the screenshot below

– First Offense – Warning

– Second Offense – Warning

– Third Offense – Invalidation from voting for a period to be determined – Vote invalidation and disabled login to the PUNK Armada DAO DAPP

Part 3 – The PUNK Armada DAO Authentication Process

– PUNK Armada DAO Authentication Process Introduction 

– PUNK Armada DAO Authentication Process Steps

PUNK Armada DAO Authentication Process Introduction – The PUNK Armada DAO authentication process leverages Web3 technology and Passport.js to provide a secure and decentralized login mechanism, and there are five steps to member authentication

PUNK Armada DAO Authentication Process Steps – There are five steps in the PUNK Armada DAO authentication process

– Step 1 – Member Initiates Login – The user attempts to log in using their Ethereum wallet. This process starts from the frontend application, which prompts the user to sign a unique message using their wallet

– Step 2 – Message Signing – The frontend generates a unique nonce (a random string) and asks the user to sign it using their private key. This signed message is then sent to the backend for verification

– Step 3 – Backend Verification – The backend, built with NestJS, uses Passport.js with a custom Web3 strategy to verify the signed message. The backend extracts the wallet address from the signed message, validates the signature using Ethers.js to ensure it matches the generated nonce, and checks if the wallet address exists in the database. If not, a new user record is created

– Step 4 – Token Generation – Upon successful verification, the backend generates a JWT (JSON Web Token) containing the user’s wallet address and other relevant information. This token is sent back to the frontend

– Step 5 – Secure Session Management – The frontend stores the JWT, typically in local storage or cookies, to manage the user’s session. This token is used for authenticated requests to the backend, ensuring secure access to protected resources. This process ensures that only the rightful owner of an Ethereum wallet can log in, leveraging the security properties of blockchain and cryptographic signatures

Part 4 – The PUNK Armada DAO Technology Stack

– PUNK Armada DAO Technology Stack Introduction

– NestJS

– GraphQL

– Prisma

– Ethers.js

– Reservoir API

PUNK Armada DAO Technology Stack Introduction – NestJS, GraphQL, Prisma, Ethers.js, and the Reservoir API each play a pivotal role in developing the comprehensive technology stack that is the PUNK Armada DAO

NestJS – This framework is chosen for its scalability and out-of-the-box application architecture which promotes clean code and modular structure. It supports TypeScript, which provides strong typing, aiding in creating more reliable code that’s easier to refactor and maintain. NestJS leverages decorators and metadata, providing a clear and structured way to handle aspects such as dependency injection, middleware, and request handling

GraphQL – This API technology is critical for facilitating dynamic data retrieval, allowing clients to fetch precisely what they need, which is incredibly efficient for the data-heavy nature of blockchain interfaces. GraphQL’s type system and schema ensure that the data is validated and predictable, making it easier to maintain and evolve APIs over time

Prisma – As the ORM for the application, Prisma offers comprehensive database schema management, straightforward data modeling, and migrations, alongside generating client libraries that facilitate safe and practical database queries. Prisma integrates seamlessly with NestJS, enabling efficient and type-safe database interactions and reducing boilerplate code

Ethers.js – It is employed to interact with the Ethereum blockchain. Ethers.js simplifies the process of sending transactions, interacting with smart contracts, and managing blockchain-related data, ensuring seamless integration of blockchain functionalities within the application. It supports a wide range of Ethereum-compatible blockchains, making it versatile for various use cases

Reservoir API – Reservoir API is a standard utilized by NFT marketplaces for a wide range of functionalities. It allows the platform to:

– Verify Ownership – Confirm whether a user owns specific NFTs required for participation in DAO governance

– Fetch Market Data – Retrieve real-time market information on NFTs, including recent sales, transfers, and current valuations, helping users make informed decisions based on the latest data

– List and Trade NFTs – Provide users the ability to list their NFTs for sale and trade them seamlessly within the platform. Reservoir API supports extensive trading capabilities, ensuring a smooth and efficient user experience

– Marketplaces Standard – As the standard for many marketplaces, it ensures compatibility and integration with other NFT trading platforms, enhancing the liquidity and reach of NFTs managed within the DAO

II. PUNK Armada DAO DAPP Frontend Documentation

Part 1 – Initial Screen – PUNK Armada DAPP Launched & Database Initialized

Part 2 – PUNK Armada DAO Login Process With MetaMask

Part 3 – Logged In Screen – PUNK Armada NFT Display & DAO Members List

Part 4 – The Proposals List – Open & Closed PUNK Armada DAO Proposals

Part 5 – The PUNK Armada DAO Voting Process – Options, Model & Actions

Part 6 – Admin Only – Creating & Submitting PUNK Armada DAO Proposals

Part 1 – Initial Screen – PUNK Armada DAPP Launched & Database Initialized

– Introduction To The Initial Screen 

– Initial Screen Display Elements 

Introduction To The Initial Screen – This initial screen provides a clear and structured layout that allows users to understand the status of the DAO, navigate through different sections, and connect their wallets to participate in DAO activities. See a screenshot of the initial user screen below

Initial Screen Display Elements – When the PUNK Armada DAO application is first launched and the database is initialized, the initial screen displays the following elements: Header, PUNK Armada DAO Description, User Wallet Information, Navigation Tabs, and Footer

– Header – Logo, DAO Name, “Connect” Button – The top-left corner features the PUNK Armada DAO logo and the name of the DAO. Connect Button – The top-right corner has a “Connect” button that allows users to connect their Web3 wallet to the application

– PUNK Armada DAO Description – Introductory Text – Below the header, there is a brief description of the DAO stating, “The PUNK Armada DAO is a collective for Web3 entrepreneurs”

– User Wallet Information – Wallet Address, Network Indicator, NFT Voting Power, and the FAQ. Wallet Address – The user’s wallet address is displayed in a shortened format, with the first and last few characters visible (e.g., “0xe507…0E542”). Network Indicator – An icon or text indicating the network the wallet is connected to (e.g., “Mainnet”). NFT Voting Power – A button or link labeled “NFT Voting Power” that provides information about the user’s voting power based on their NFTs. FAQ Button – A button or link labeled “FAQ” that redirects users to a Frequently Asked Questions page

– Navigation Tabs – Navigation Tabs include Created Proposals, In Progress, and Members. Created Proposals – A tab labeled “Created Proposals” that, when selected, displays the proposals created within the DAO. If there are no proposals, a message “No proposals found” is displayed. In Progress – A tab labeled “In Progress” that shows ongoing proposals. If there are no ongoing proposals, a similar message “No proposals found” is displayed. Members – A tab labeled “Members” that lists the current members of the DAO. If there are no members, a message “No users found” is displayed. Footer – The Footer includes Social Links to the DAO’s Discord, Twitter, and other social media platforms and Copyright Information. Text displaying copyright information is for the year 2024, attributed to “4762=4762. All rights reserved”

Part 2 – PUNK Armada DAO Login Process With MetaMask

– Login Process Introduction 

– Steps For Logging Into MetaMask

Login Process Introduction – This process ensures secure authentication by proving wallet ownership without exposing private keys, leveraging blockchain technology for decentralized identity verification

Steps For Logging Into MetaMask – The login process with MetaMask and nonce signing involves six steps

– Step 1 – User initiates login – The user clicks on the “Connect” button on the initial screen and a modal window appears titled “Choose your wallet,” presenting options such as MetaMask, Coinbase Wallet, and WalletConnect. See an image of this screen below

– Step 2 – User selects MetaMask – The user selects MetaMask from the list of available wallet options and then a connection request is initiated through the MetaMask extension

– Step 3 – MetaMask connection prompt – MetaMask prompts the user to select the account(s) they wish to connect to the application and then the user selects the desired account(s) and clicks “Next”

– Step 4 – MetaMask signature request – The user is prompted by MetaMask to sign a nonce, or message, to prove ownership of the wallet and to prevent replay attacks. See a screenshot of the signature request below

– Step 5 – User signs the message – The user reviews the message and clicks “Sign” to proceed, at which point MetaMask generates a digital signature using the user’s private key, which is then sent back to the application for verification

– Step 6 – Backend verification – The backend of the DAPP verifies the signature to authenticate the user. If the signature is valid, the user is authenticated and logged into the application

Part 3 – Logged In Screen – PUNK Armada NFT Display & DAO Members List

– PUNK Armada NFT Display

– PUNK Armada DAO Members List Display Elements

PUNK Armada NFT Display – The NFT display section is on the right side of the logged in screen, and presents a visual representation of the user’s owned PUNK Armada NFTs, including the NFT’s name and ID. In addition, the number of votes the NFT has are displayed. See a screenshot of the PUNK Armada NFT display below

PUNK Armada DAO Members List Display Elements – Each PUNK Armada DAO member’s entry in the Members List includes three elements – the Profile Image, the Wallet Address, and the Online Status Indicator. There is also a load more button at the bottom of the list, which allows users to display members beyond the initial set. See a screenshot of the PUNK Armada DAO Members List below, followed by a brief description of the related design elements

– Profile Image – A unique icon or avatar representing the member. This might be a generated or pre-set image to visually distinguish each member

– Wallet Address – The member’s wallet address is displayed in a shortened format to enhance readability. Only the first few and last few characters of the address are shown (e.g., “0x09…7cb7”)

– Online Status Indicator – A small dot next to the wallet address indicates the member’s online status. A blue dot suggests the member is currently online or active

Part 4 – The Proposals List – Open & Closed PUNK Armada DAO Proposals

– Created Proposals

– In Progress Proposals

Created Proposals – This section lists all proposals created within the PUNK Armada DAO. At the top of the “Created Proposals” section, there is a state filter that allows users to switch between viewing “IN_PROGRESS” and “CLOSED” proposals. Users can interact with the proposals by reading the descriptions and voting on the options provided. Below the reader will find a shot of the closed PUNK Armada DAO proposals screen

In Progress Proposals – Elements of an in progress proposals include the Proposal Title, a Description of the proposal, a Status indicator, and a “More” button that allows users to view additional details about the proposal

Part 5 – The PUNK Armada DAO Voting Process – Options, Model & Actions

– Voting Option Details

– Initiating A Vote

– Voting Modal

– Selecting NFTs For Voting

– Voting Actions

– Screenshot Of Proposal List & Votes Updated 

Voting Option Details – Each proposal includes multiple voting options with the following details:

– Option Title – The title of the voting option (e.g., “Yes” or “No”)

– Option Description – A detailed description of what the voting option entails

– Vote Count – The number of votes cast for each option and the corresponding percentage of vote power

– Vote Button – A button labeled “Vote” that allows users to cast their vote for the specific option

Initiating A Vote – The user clicks on the “Vote” button next to the desired voting option in the proposal. This action triggers the voting modal to open

Voting Modal – The header displays the title of the proposal, while the proposal description helps the user review the proposal context of a selected voting option

Selecting NFTs For Voting – Each PUNK Armada NFT has a checkbox next to it, allowing the user to select which NFTs he/she wants to use for voting. A “Select All” option is available for users who want to use all their eligible NFTs for voting

Voting Actions – Cancel or Confirm?

– “Cancel” Button – This button allows the user to exit the voting process without casting a vote

– “Confirm Vote” Button – Clicking this button confirms the vote with the selected PUNK Armada NFTs, triggering the backend to record the vote and then ensuring that the selected NFTs are valid and not listed for sale (soft staked)

Screenshot Of Proposal List & Votes Updated – “Vote submitted successfully” seen in the screenshot below

Part 6 – Admin Only – Creating & Submitting PUNK Armada DAO Proposals

– Accessing The Proposal Creation Form

– The Proposal Creation Form

– Adding Voting Options

– Submitting The Proposal

– Proposal Creation Confirmation

– Backend Processing 

Accessing The Proposal Creation Form – The user navigates to the “New Proposal” tab from the main navigation menu, clicking the “New Proposal” tab opens the proposal creation form. See a screenshot of this below

The Proposal Creation Form – The proposal creation form includes the following input elements – Title, Description, and Duration

– Title input – An input field where the user can enter the title of the proposal. Example: “Ordinals”

– Description input – A text area where the user can provide a detailed description of the proposal. Example: “In the case where we decide to launch a collection on Ordinals. Yes we want to launch a collection on Ordinals, but is now the right time?”

– Duration input – An input field where the user can specify the duration of the proposal in days. Example: “7” (for 7 days)

Adding Voting Options – Here the user will complete voting option inputs for Title, Description, and “Add Another Option”

– Option title input – Input fields where the user can add the titles of different voting options. Examples: “Yes”, “No”, “Maybe”

– Option description input – Text area fields where the user can provide descriptions for each voting option. Examples: “I want to launch an Ordinals collection now”, “I don’t want to launch an Ordinals collection now”, “I am unsure about launching an Ordinals collection now”

– “Add Another Option” Button – Clicking this button adds additional input fields for more voting options. Limit – The user can add up to a predefined maximum number of options (e.g., 3)

Submitting The Proposal – Clicking the “Create Proposal” button at the bottom of the form submits the proposal to the backend of the PUNK Armada DAO for proposal creation

Proposal Creation Confirmation – A notification appears at the top-right corner of the screen, confirming that the proposal has been created successfully with a message “Proposal created successfully”. See a screenshot of this below

Backend Processing – The backend validates that the user is an admin and that the input data is complete and correct. If validation is successful, the backend creates the proposal and stores it in the database and a cron job is scheduled to run at the proposal’s closing date to tally votes and finalize the proposal’s outcome

III. PUNK Armada DAO DAPP Backend Documentation

– Part 1 – PUNK Armada DAO Account Creation

– Part 2 – PUNK Armada DAO Authentication

– Part 3 – Fetching PUNK Armada DAO Proposal List 

– Part 4 – Fetching User’s PUNK Armada NFTs 

– Part 5 – Fetching PUNK Armada DAO Members 

– Part 6 – PUNK Armada DAO Proposal Creation

– Part 7 – Cron Job for PUNK Armada DAO Proposal Closure

Part 1 – PUNK Armada DAO Account Creation

– PUNK Armada DAO Account Creation Flow Steps

– PUNK Armada DAO Account Creation Elements

– PUNK Armada DAO Account Creation Process Diagram

– PUNK Armada DAO Account Creation Flow Diagram

PUNK Armada DAO Account Creation Flow Steps – There are thirteen steps in the PUNK Armada DAO account creation process

– Step 1 – User initiates registration – The user begins the registration process in the application

– Step 2 – Frontend generates a nonce – The frontend generates a unique nonce to be used for authentication

– Step 3 – User signs the nonce with their Ethereum wallet – The user uses their Ethereum wallet to sign the generated nonce

– Step 4 – Frontend sends the signed message and wallet address to the backend – The frontend sends the signed message and the user’s wallet address to the backend for verification

– Step 5 – Backend verifies the signature – The backend verifies the authenticity of the signed message using the wallet address

– Step 6 – Backend checks if the user exists in the database – The backend checks if the user’s wallet address already exists in the database

– Step 7 – If the user does not exist, the backend creates a new user – If the user does not exist, the backend creates a new user record in the database

– Step 8 – Backend requests user tokens from the Reservoir API – The backend makes a request to the Reservoir API to obtain tokens associated with the user’s wallet address

– Step 9 – The Reservoir API responds with the user’s tokens – The Reservoir API responds with the user’s tokens

– Step 10 – Backend stores the user’s tokens in the database – The backend stores the user’s tokens in the database, associating them with the user’s record

– Step 11 – Backend generates a JWT token – The backend generates a JWT (JSON Web Token) for the user’s session

– Step 12 – Backend sends the JWT token to the frontend – The backend sends the generated JWT token to the frontend

– Step 13 – Frontend stores the JWT token – The frontend stores the JWT token to maintain the user’s session

PUNK Armada DAO Account Creation Elements – Below PUNK Armada DAO members will find a brief description of the elements of DAO account creation

– User – Initiates the registration process and signs the nonce

– Frontend – Generates the nonce, sends the signed message, and stores the JWT token

– Backend – Verifies the signature, checks the user’s existence, creates the user, requests tokens, stores tokens, and generates the JWT token

– Database – Stores user information and tokens obtained from the Reservoir API

– Reservoir API – Provides the user’s tokens in response to the backend’s request

PUNK Armada DAO Account Creation Process Diagram – Below PUNK Armada DAO members will find a diagram of the DAO account creation process

PUNK Armada DAO Account Creation Flow Diagram – Below PUNK Armada DAO members will find a diagram illustrating the flow of the DAO account creation process 

Part 2 – PUNK Armada DAO Authentication

– PUNK Armada DAO Authentication Flow Steps

– PUNK Armada DAO Authentication Elements

– PUNK Armada DAO Authentication Process Diagram

– PUNK Armada DAO Authentication Flow Diagram

PUNK Armada DAO Authentication Flow Steps – There are thirteen steps in the PUNK Armada DAO authentication process

– Step 1 – User initiates login – The user begins the login process in the application

– Step 2 – Frontend generates a nonce – The frontend generates a unique nonce to be used for authentication

– Step 3 – User signs the nonce with their Ethereum wallet – The user uses their Ethereum wallet to sign the generated nonce

– Step 4 – Frontend sends the signed message and wallet address to the backend – The frontend sends the signed message and the user’s wallet address to the backend for verification

– Step 5 – Backend verifies the signature – The backend verifies the authenticity of the signed message using the wallet address

– Step 6 – Backend checks if the user exists in the database – The backend checks if the user’s wallet address already exists in the database

– Step 7 – If the user does not exist, the backend creates a new user – If the user does not exist, the backend creates a new user record in the database

– Step 8 – Backend requests user tokens from the Reservoir API – The backend makes a request to the Reservoir API to obtain tokens associated with the user’s wallet address

– Step 9 – The Reservoir API responds with the user’s tokens – The Reservoir API responds with the user’s tokens

– Step 10 – Backend stores the user’s tokens in the database – The backend stores the user’s tokens in the database, associating them with the user’s record

– Step 11 – Backend generates a JWT token – The backend generates a JWT (JSON Web Token) for the user’s session

– Step 12 – Backend sends the JWT token to the frontend – The backend sends the generated JWT token to the frontend

– Step 13 – Frontend stores the JWT token – The frontend stores the JWT token to maintain the user’s session

PUNK Armada DAO Authentication Elements – Below PUNK Armada DAO members will find a brief description of the elements of the DAO authentication process

– User – Initiates the login process and signs the nonce

– Frontend – Generates the nonce, sends the signed message, and stores the JWT token

– Backend – Verifies the signature, checks the user’s existence, creates the user if necessary, requests tokens, stores tokens, and generates the JWT token

– Database – Stores user information and tokens obtained from the Reservoir API

– Reservoir API – Provides the user’s tokens in response to the backend’s request

PUNK Armada DAO Authentication Process Diagram – Below PUNK Armada DAO members will find a diagram of the DAO authentication process

PUNK Armada DAO Authentication Flow Diagram – Below PUNK Armada DAO members will find a diagram illustrating the flow of the DAO authentication process

Part 3 – Fetching PUNK Armada DAO Proposal List 

– Fetching PUNK Armada DAO Proposal List Flow Steps

– Fetching PUNK Armada DAO Proposal List Elements

– Fetching PUNK Armada DAO Proposal List Process Diagram

– Fetching PUNK Armada DAO Proposal List Flow Diagram

Fetching PUNK Armada DAO Proposal List Flow Steps – There are eight steps in the PUNK Armada DAO proposal list fetching process

– Step 1 – User initiates a request to view proposals – The user begins the process to view the list of proposals

– Step 2 – Frontend sends a request to the backend – The frontend sends a request to the backend to fetch the list of proposals, including a filter for status (IN PROGRESS or CLOSED)

– Step 3 – Backend receives the request – The backend receives the request to fetch proposals with the specified status filter

– Step 4 – Backend queries the database for proposals – The backend queries the database to retrieve the list of proposals that match the specified status

– Step 5 – Database responds with proposals – The database sends the list of proposals back to the backend

– Step 6 – Backend formats the proposals – The backend formats the retrieved proposals, possibly adding additional data or metadata

– Step 7 – Backend sends the formatted proposals to the frontend – The backend sends the list of formatted proposals to the frontend

– Step 8 – Frontend receives and displays the proposals – The frontend receives the list of proposals and displays them to the user

Fetching PUNK Armada DAO Proposal List Elements – Below PUNK Armada DAO members will find a brief description of the elements of the DAO proposal list fetching process

– User – Initiates the request to view the list of proposals

– Frontend – Sends the request to the backend with the status filter and displays the proposals received

– Backend – Receives the request, queries the database with the status filter, formats the proposals, and sends them back to the frontend

– Database – Stores and retrieves proposal information as requested by the backend, filtering by status (IN PROGRESS or CLOSED)

Fetching PUNK Armada DAO Proposal List Process Diagram – Below PUNK Armada DAO members will find a diagram of the DAO proposal list fetching process

Fetching PUNK Armada DAO Proposal List Flow Diagram – Below PUNK Armada DAO members will find a diagram illustrating the flow of the DAO proposal list fetching process 

Part 4 – Fetching User’s PUNK Armada NFTs 

– Fetching User’s PUNK Armada NFTs Flow Steps

– Fetching User’s PUNK Armada NFTs Elements

– Fetching User’s PUNK Armada NFTs Process Diagram

– Fetching User’s PUNK Armada NFTs Flow Diagram

Fetching User’s PUNK Armada NFTs Flow Steps – There are eight steps in the PUNK Armada DAO user NFT fetching process

– Step 1 – User initiates a request to view their NFTs – The user begins the process to view the list of their NFTs

– Step 2 – Frontend sends a request to the backend – The frontend sends a request to the backend to fetch the user’s NFTs

– Step 3 – Backend receives the request – The backend receives the request to fetch the user’s NFTs

– Step 4 – Backend queries the database for user’s NFTs – The backend queries the database to retrieve the NFTs associated with the user’s wallet address

– Step 5 – Database responds with user’s NFTs – The database sends the list of NFTs owned by the user back to the backend

– Step 6 – Backend processes and formats the NFT data – The backend processes and formats the NFT data received from the database

– Step 7 – Backend sends the formatted NFT data to the frontend – The backend sends the list of formatted NFTs to the frontend

– Step 8 – Frontend receives and displays the NFTs – The frontend receives the list of NFTs and displays them to the user

Fetching User’s PUNK Armada NFTs Elements – Below PUNK Armada DAO members will find a brief description of the elements of the DAO user NFT fetching process

– User – Initiates the request to view their NFTs

– Frontend – Sends the request to the backend and displays the NFTs received

– Backend – Receives the request, queries the database, processes the NFT data, and sends it back to the frontend

– Database – Stores and retrieves the user’s NFTs as requested by the backend

Fetching User’s PUNK Armada NFTs Process Diagram – Below PUNK Armada DAO members will find a diagram of the DAO user NFT fetching process

Fetching User’s PUNK Armada NFTs Flow Diagram – Below PUNK Armada DAO members will find a diagram illustrating the flow of the DAO user NFT fetching process 

Part 5 – Fetching PUNK Armada DAO Members 

– Fetching User’s PUNK Armada DAO Members Flow Steps

– Fetching User’s PUNK Armada DAO Members Elements

– Fetching User’s PUNK Armada DAO Members Process Diagram

– Fetching User’s PUNK Armada DAO Members Flow Diagram

Fetching User’s PUNK Armada DAO Members Flow Steps – There are eight steps in the PUNK Armada DAO “fetching members” process

– Step 1 – User initiates a request to view the members list – The user begins the process to view the list of members

– Step 2 – Frontend sends a request to the backend – The frontend sends a request to the backend to fetch the list of members

– Step 3 – Backend receives the request – The backend receives the request to fetch the members list

– Step 4 – Backend queries the database for non-banned members – The backend queries the database to retrieve the members who are not banned

– Step 5 – Database responds with non-banned members – The database sends the list of non-banned members back to the backend

– Step 6 – Backend processes and formats the members data – The backend processes and formats the members data received from the database

– Step 7 – Backend sends the formatted members data to the frontend – The backend sends the list of formatted non-banned members to the frontend

– Step 8 – Frontend receives and displays the members – The frontend receives the list of non-banned members and displays them to the user

Fetching User’s PUNK Armada DAO Members Elements – Below PUNK Armada DAO members will find a brief description of the elements of the DAO “fetching members” process

– User – Initiates the request to view the list of members

– Frontend – Sends the request to the backend and displays the members received

– Backend – Receives the request, queries the database, processes the members data, and sends it back to the frontend

– Database – Stores and retrieves member information, ensuring only non-banned members are retrieved as requested by the backend

Fetching User’s PUNK Armada DAO Members Process Diagram – Below PUNK Armada DAO members will find a diagram of the DAO “fetching members” process

Fetching User’s PUNK Armada DAO Members Flow Diagram – Below PUNK Armada DAO members will find a diagram illustrating the flow of the DAO “fetching members” process 

Part 6 – PUNK Armada DAO Proposal Creation

– PUNK Armada DAO Proposal Creation Flow Steps

– PUNK Armada DAO Proposal Creation Elements

– PUNK Armada DAO Proposal Creation Process Diagram

– PUNK Armada DAO Proposal Creation Flow Diagram

PUNK Armada DAO Proposal Creation Flow Steps – There are twelve steps in the PUNK Armada DAO proposal creation process

– Step 1 – Admin user initiates the request to create a proposal – The admin user begins the process to create a new proposal

– Step 2- Frontend sends the proposal creation request to the backend – The frontend sends the proposal details to the backend

– Step 3 – Backend receives the request – The backend receives the request to create a new proposal

– Step 4 – Backend checks if the user is an admin – The backend verifies if the user has admin privileges

– Step 5 – If the user is not an admin – The backend returns an error indicating that the user does not have the necessary permissions to create a proposal. Error response then sent to frontend – the frontend displays an error message to the user

– Step 6 – If the user is an admin – The backend proceeds to create the proposal

– Step 7 – Backend saves the proposal to the database – The backend saves the new proposal details to the database

– Step 8 – Backend schedules a cron job for the proposal – The backend schedules a cron job to run until the proposal’s closing date

– Step 9 – Database stores the proposal – The proposal details are stored in the database

– Step 10 – Cron job is scheduled – The cron job is set to monitor and manage the proposal until its closing date

– Step 11 – Backend sends a success response to the frontend – The backend sends a confirmation that the proposal has been successfully created

– Step 12 – Frontend receives and displays the success message – The frontend shows a success message to the user indicating that the proposal has been created

PUNK Armada DAO Proposal Creation Elements – Below PUNK Armada DAO members will find a brief description of the elements of the DAO proposal creation process

– Admin User – Initiates the proposal creation process

– Frontend – Sends the proposal creation request to the backend and displays the result

– Backend – Receives the request, checks if the user is an admin, creates the proposal if the user is an admin, schedules the cron job, and sends a response back to the frontend

– Database – Stores the proposal information

– Cron Job Scheduler – Schedules and manages the cron job to run until the proposal’s closing date

PUNK Armada DAO Proposal Creation Process Diagram – Below PUNK Armada DAO members will find a diagram of the DAO proposal creation process

PUNK Armada DAO Proposal Creation Flow Diagram – Below PUNK Armada DAO members will find a diagram illustrating the flow of the DAO proposal creation process 

Part 7 – Cron Job For PUNK Armada DAO Proposal Closure

– Cron Job For PUNK Armada DAO Proposal Closure Flow Steps

– Cron Job For PUNK Armada DAO Proposal Closure Elements

– Cron Job For PUNK Armada DAO Proposal Closure Process Diagram

– Cron Job For PUNK Armada DAO Proposal Closure Flow Diagram

Cron Job For PUNK Armada DAO Proposal Closure Flow Steps – There are nine steps in the PUNK Armada DAO proposal closure process

– Step 1 – Admin creates a proposal – The admin user creates a new proposal, and the proposal details are saved in the database

– Step 2 – Backend schedules a cron job – A cron job is scheduled to run at the proposal’s closing date

– Step 3 – Cron job is triggered on the proposal’s closing date – The cron job is activated when the proposal’s closing date is reached

– Step 4 – Cron job retrieves the proposal and votes – The cron job retrieves the proposal details and all associated votes from the database

– Step 5 – Cron job validates the soft staking of NFTs – For each vote, the cron job verifies if the NFTs used in the vote are not listed for sale (soft staked) at the moment of vote closing

– Step 6 – Cron job calculates the final decision – Based on the validated votes, the cron job calculates the final decision of the proposal

– Step 7 – Cron job updates the proposal status – The proposal status is updated in the database to reflect the final decision (e.g., APPROVED, REJECTED)

– Step 8 – Cron job stores the final results – The final results and any relevant data are stored in the database

– Step 9 – Notification to admin and participants – Optional – Notifications are sent to the admin and participants about the final decision

Cron Job For PUNK Armada DAO Proposal Closure Elements – Below PUNK Armada DAO members will find a brief description of the elements of the DAO proposal closure process

– Admin User – Creates a new proposal

– Backend – Schedules the cron job upon proposal creation

– Database – Stores proposal details, votes, and final results

– Cron Job Scheduler – Schedules and triggers the cron job at the proposal’s closing date

– Cron Job Execution – Retrieves the proposal and votes from the database, validates the soft staking of NFTs for each vote, calculates the final decision based on the validated votes, updates the proposal status in the database, and then stores the final results in the database

– Notification System (optional) – Sends notifications to the admin and participants about the final decision

Cron Job For PUNK Armada DAO Proposal Closure Process Diagram – Below PUNK Armada DAO members will find a diagram of the DAO proposal closure process

Cron Job For PUNK Armada DAO Proposal Closure Flow Diagram – Below PUNK Armada DAO members will find a diagram illustrating the flow of the DAO proposal closure process 

…

Thanks for reading!