The Portal Loop

[moul]

https://github.com/orgs/gnolang/projects/13

Objective

Create a robust markdown render for Gno.land Home and Launch pages, combining both static elements and dynamic DAO-generated data. This render will form the basis for creating a seamless loop around feedback, testing, and iterative development to constantly enhance local development and, in turn, enhance the Gno.land website.

The Portal Loop

The Portal Loop is a cyclical process aimed at continuously refining our work based on actionable feedback. It commences with clear directives from the leadership, pointing us towards the envisaged outcome. Open dialogue, testing, dogfooding, and constant feedback are its core pillars.

Detailed Working

1. Automated Releases: Trigger automatic releases based on GitHub merges, specific timings, or tags.
2. Backup and Rebuild: Before each release, backup last transactions. Generate a new genesis using the recent transactions, which also considers generating balances for any address involved in a transaction.
3. Chain Initiation: Initiate a new chain, embedding GitHub-enforced contracts, subsequently launching genesis transactions sequentially, followed by running the chain.
4. Optimization: Shorten the display time for the "maintenance" page. This process should be automated from nginx.
5. Transaction Fetching: Develop efficient mechanisms, like an improved version of gnotxsync, to fetch the last transactions swiftly. Also, explore resume options.
6. Genesis Builder: Create a system to convert a history into a functional genesis. Initially, a simple method can be adopted, with future plans of integrating advanced features like embedding transaction metadata (height, timestamps, etc.).
7. Contract Development: I (@moul) will spearhead the drafting of foundational contracts which will form the new homepage structure. The goal is to construct the homepage using UI blocks extracted from various contracts.

Expected Outcomes

Upon successful implementation of the Portal Loop, we anticipate:

• An enriched local development environment packed with up-to-date contracts and on-chain data.
• Transformation of gno.land into a central hub not just for project discovery but also for dynamic data interaction.
• A vibrant community-driven platform where everyone is encouraged to enhance the website, rectify bugs, and introduce new contracts.

Important Note

This dedicated testnet is a staging platform primarily for the core team to display their achievements. While it doesn't offer full network support (e.g., no indexers), users can still experiment with this staging testnet. However, for conventional operations, users should consider other testnets (like test3, test4) or set up local nodes.

---

Depends on:

• Homepage contract + gnoweb improvements MVPs; feat: portal loop's main contracts and gnoweb improvements #1176 (lead by @moul)
• Eventually-consistent staging; New eventually-consistent staging (for local dev and gno.land) #1131 (lead by @zivkovicmilos) chore(misc/loop): Setup the portal loop infra #1400
• Genesis manipulation tools: PoC for Genesis Manipulation Libraries and Tools #1189 (lead TBD)
• store history on txports repo Back up Portal Loop transaction data tx-exports#15

Next:

• Monitoring agent: Portal Loop: monitoring agent/oracle #1443
• GnoSDK structure: feat: bootstrap tm2demo #1105
• Gnoweb improvements: META Gnoweb improvements #1187 (good first issues, anyone, non-exhaustive)
• Preserve timestamp in history and replay: gnodev time.Now() values are not preserved on reload #1509
• DAO Contracts MVPs (lead by @moul

[tbruyelle]

Create a robust markdown render for Gno.land Home and Launch pages, combining both static elements and dynamic DAO-generated data.

Regarding this objective, I was wondering why #903 isn't mentioned ?