Gordianic — Getting Started
From claiming your community domain to creating a DAO, and practical technical examples for governing its website and membership.
1. Claim a Gordianic Domain
The first step is to claim a domain for your community.
Your domain gives your project its own space within Gordianic, such as:
You can use this space to present your idea, share information and give people a place to discover your community.
You do not need to deploy a smart contract or create a DAO yourself.
2. Build Your Initial Community
After claiming your domain, invite other people to participate.
A minimum of 10 participants is required before Gordianic proceeds with creating the DAO.
This threshold is intentionally small. It allows new ideas to get started without requiring a large existing audience, while ensuring that a DAO begins with an actual group of participants rather than a single person.
3. DAO Creation
Once your community reaches at least 10 participants, Gordianic can proceed with creating the DAO.
The DAO provides the community with a transparent governance structure for making decisions together.
Gordianic currently uses blockchain infrastructure on Polygon and governance infrastructure based on Aragon OSx.
Because Gordianic is in beta, the exact DAO configuration may evolve as we gain experience with operational DAOs.
4. Community Governance
Once a DAO is operational, its participants can use governance to make decisions about the community.
Depending on the DAO’s configuration, this may include decisions about:
- the content displayed on the community domain
- adding participants
- community rules
- project direction
- technical changes
The aim is to give communities meaningful control without requiring participants to understand or deploy smart contracts themselves.
The current demo uses a list of approved wallet addresses for incubation governance. Joining on the website does not automatically make an address an on-chain member.
5. Becoming More Decentralized
Gordianic does not assume that every community needs its final governance structure from day one.
The first priority is to make it easy to start communities and create working DAOs.
As more Gordianic DAOs become operational, we will evaluate how communities can gain greater technical and organizational independence.
Future decentralization decisions will be based on practical experience with real communities rather than a predetermined governance model.
Beta
Gordianic is experimental software.
Features, governance configurations and technical infrastructure may change as the platform develops.
For the latest information, see the Beta Status page.
7. Governance Walkthrough
The examples below are taken from the current Demo DAO governance guide. They show how to use Aragon on Polygon mainnet to update a website destination or add members.
Connect the wallet address that has the required permission. Review the live proposal rules before signing; the thresholds and deadlines below describe the demo's current documented configuration.
8. Change the Website URL
First upload your new website to its hosting provider. The full public URL becomes the new destination for demo.gordianic.me.
- Prepare and check your website. Upload all files and open the destination URL in a private browser window. It must work without a login.
- Create a proposal. Open the demo DAO in Aragon, connect your listed wallet on Polygon, choose Create proposal, select Incubation Governance, then add a title and explanation.
- Add the action. Select the subdomain registry contract and the function
setContenthash(string,string). Enter the values below. Although the field is calledcid, the new value is a complete website URL, not an IPFS hash.
| Contract | 0x41B9b303b883AE0f7eC2bc50272AFa133D5d7E4c |
|---|---|
| Function | setContenthash(string,string) |
| label | demo |
| cid | The full new public URL, including https:// |
| Value / POL | 0 — this action sends no funds |
- Simulate and publish. Check the label and URL, simulate, then publish and confirm in your wallet. Resolve simulation errors before publishing.
- Obtain approval. For the demo's documented Incubation Governance configuration, collect 2 member approvals within the 7-day voting period.
- Wait and execute. After the approval stage advances, wait for the minimum 48-hour delay. When execution becomes available, an authorized wallet selects Execute and confirms the transaction. Reload the subdomain after its resolver cache refreshes.
If Aragon does not list the action
Add the registry by address. If necessary, turn off Only show allowed actions and locate setContenthash. This only changes what is displayed by the action picker; it does not grant permission. Simulate the proposal before publishing.
Administrator route
An authorized wallet may use the separate Admin process to propose and execute the same registry action. This route does not use the member-approval stages described above.
9. Add Members to the Address List
The incubation administrator adds approved wallet addresses. Joining a discussion or registering on the website does not automatically grant on-chain governance membership.
- Collect addresses. Ask each member for the complete Polygon-compatible
0x…wallet address they will actually use in Aragon. Verify each address with its owner. - Open the Admin process. Connect an authorized administrator wallet, choose Create proposal, then Admin. Give the proposal a title such as “Add community members”.
- Add the member action. Choose Incubation Members → Add members. If using the contract picker, select the address below and call
addAddresses(address[]).
| Contract | 0x93DE580eE1F9F26C59982ad4E4a25187CBD89959 |
|---|---|
| Function | addAddresses(address[]) |
| _members | An array with one complete 0x… wallet address per new member |
| Value / POL | 0 |
- Simulate and execute. Review the array carefully. Admin proposals can execute immediately if the connected wallet has the required permission. Confirm the status is Executed.
- Verify membership. Open the Incubation Members list in Aragon and check the added addresses. New members can participate in proposals created after addition; existing proposals use the membership snapshot from creation time.
10. Demo Contract Reference
| Component | Polygon mainnet address |
|---|---|
| Aragon DAO | 0x32D945F5D8b74aa5751F60c19D5e83C4D35180e3 |
| Subdomain registry | 0x41B9b303b883AE0f7eC2bc50272AFa133D5d7E4c |
| Incubation Members | 0x93DE580eE1F9F26C59982ad4E4a25187CBD89959 |
These addresses and function signatures are reproduced from the live demo guide as of 29 October 2026. Always verify them against the DAO's live configuration before signing a transaction. Do not reuse the demo label or demo-specific addresses for another DAO without checking its deployment.
Further reading: Aragon multisig documentation · Membership management API · PolygonScan.