Terra Classic Developer Guide: Smart Contract and DApp Development Manual

General
1

:blue_book: Proposal Summary
This proposal aims to encourage developer activity on the Terra Classic network by creating a comprehensive technical guide for building on the chain. The guide will help onboard new contributors by covering the essential tools, workflows, and integration steps for smart contract development, DApp creation, testnet usage, SDK tools, and wallet connectivity.

:bullseye: Rationale
Sustainable growth of the Terra Classic network depends on strong developer engagement.

Many new developers face difficulties due to the lack of updated or beginner-friendly technical resources.

Currently, there is no official or up-to-date “Getting Started Guide” tailored to the Terra Classic chain.

A well-prepared technical guide will build trust and lower the barrier for onboarding builders.

:pushpin: Proposed Guide Content
Overview of the Terra Classic network

Development environment setup

Terrain, LocalTerra, and Rebel-2 testnet configuration

Writing smart contracts using CosmWasm (Rust)

Web-based DApp connection using CosmJS

Wallet integration (Keplr, Terra Station)

Testing and deployment procedures

Real-world DApp examples with code

Best practices for developers

FAQ and troubleshooting section

GitHub resources and open-source templates

:busts_in_silhouette: Contributors and Process
This guide will be created by experienced developers within the Terra Classic community. Individuals like @ColeStrathclyde, @frag_dude, or others with proven technical knowledge may be invited to participate.

After governance approval, the selected contributors will be compensated based on the approved budget and defined milestones. The process will be transparent, with regular updates and draft reviews shared with the community.

The community may choose to either form a small selection committee or allow open applications from interested contributors.

:wrench: Technical Approach & Delivery
The guide will be published via GitBook, Notion, and PDF for accessibility.

It will be written in a modular format to allow future updates.

Open to community contributions and review.

:ballot_box_with_ballot: Voting Options
:white_check_mark: Yes – Approve and begin guide development

:cross_mark: No – Reject the proposal

:locked: No with Veto – Reject and prevent similar proposals from being resubmitted

:handshake: Abstain – Neutral / no opinion

2 Likes
2

Maybe you should post this in the Proposal section instead of General.

I guess I could set up to some kind of Wiki page or Gitbook and put some of my knowledge in there.

Depends how much time I have at my disposal :flushed_face:

2 Likes
3

I actually think that would be a good idea. I personally think this should go in the core repository though. If the wiki or gitbook was managed through the repository like how the Terra Docs were, that would be good too.

2 Likes
4

Thanks @frag_dude :raising_hands:
Your contribution would seriously boost the quality of this guide. It’d be great to have you involved whenever you have time. I also think the GitBook idea fits perfectly!

1 Like