archway-network / archway Goto Github PK

View Code? Open in Web Editor NEW

68.0 13.0 95.0 5.92 MB

Archway Network

Home Page: https://archway.io

License: Other

Go 94.32% Makefile 1.17% Dockerfile 0.02% Shell 0.69% Rust 3.73% Smarty 0.07%

blockchain cosmos-sdk golang cosmwasm archway go wasm

archway's People

Contributors

Stargazers

Watchers

Forkers

smolnba oxcryptos dewrin txuwdzu di7778 qustomqure paddymc wotori sienrik15 onishchenkotetyana godyfack adovzhenkoo lexelmundo insomnia34 chris-ricketts mafiacryptox alliwarrior warasa126 chxrlqv995ob3 gilla6818 dscrqcf361ab3 halbornteam tecnuk tecnodes-network caesarcarol micro-sd dragontryy helenistic endorphinel dappadandev alipostaci2001 niocris suhasagg alessandro-baldassarre pa1amar 88mikhail88 do11i fatalissst aidar100 irinaworkm dmi3yk zanicar vidhanarya shahbazn jamesatomc faddat mrshukla1805 jlehtimaki ramdek18 ironman973 freeman8914 linmoonbot golden-ratio-staking tundraw clasik32 violett21 l0vd2 ezstaking vikidublin sgfractal mms-team dmitryvolev angiesandiro kayano monikacat maximilianuos discoverdefiteam nnsw3 milakan98 shashank-priyadarshi spoo-bar andreacorsaria narko2t annarko rishardn svetanat lehamart vermchannt atamestchange blacksandtech solidsnake34 deljavi937 elennark ivanovichv tanyakal dashkanar malynark efimovst poyrazturkuaz tircimahmut bytesingsong

archway's Issues

rename go.mod once network name is decided

https://github.com/cosmos-zone/zone/blob/master/go.mod#L1 needs to be edited to match the network's name

Better design of gastracker module

Re-designing how gastracker works by upgrading to newer version of cosmos-sdk with pre and post tx hook support.

This will include:
- Upgrade to newer version of cosmos-sdk
- Rewrite gastracker with more robust design
- Update gastracker tests

rename bech32prefix once network name is decided

https://github.com/cosmos-zone/zone/blob/master/app/app.go#L100

Technical Archiecture Overview

Add Config Flag

Archwayd CLI is missing config flag to manage config through the CLI

Improve CSS design of docs.archway.io

Identify Ideal Economic Parameters

Figure out economy parameters with help of data modeling and other team members help (Find an answer to these questions: 1. Should it be hardcoded? 2. Should it be controlled via governance? 3. Should it be calculated programmatically? if yes, how?)

We have to identify ideal value of following:
- Percentage of inflation reward that can go to dev
- Percentage of gas rebate that can go to dev 
- Max Percentage of smart contract premium we can charge

┆Issue is synchronized with this Jira Task by Unito

Docs Website Design Upgrade

Improve the design of the docs.archway.io home landing page. Design TBD

Lightpaper

Create - Tutorials

Second Video Tutorial

CosmWasm Logging Output

Docs Website Improvements

Developer Rewards System Overview

Create infrastructure as code

Overview:
In order to create a network simulation it should be able to deploy infrastructure in a single command to both local setups & cloud setups.

dApp Starter Code Templates

Vanilla Archway Testnet

A vanilla starport testnet with CosmWasm implemented

Add script to simulate network traffic

Overview:
In order to back our economical model we require a simulation test that can interact with the reward models and provide the accurate results.

Universe - Overview

Can’t store smart contracts

It seems that deploying contracts its failing for Titus & Constantine.

Local setups work inconsistently.

Common error reported

confirm transaction before signing and broadcasting [y/N]: y
{"height":"37","txhash":"3874989C7A9C3FCB693BFD302A8C5B24B7902FC5C32FC2EFEBCBB918D35CDE58","codespace":"wasm","code":2,"raw_log":"failed to execute message; message index: 0: Error calling the VM: Error during static Wasm validation: Wasm contract doesn't have required export: \"interface_version_5\". Exports required by VM: [\"interface_version_5\", \"instantiate\", \"allocate\", \"deallocate\"]. Contract version too old for this VM?: create wasm contract failed","gas_wanted":"tel:2000000","gas_used":"770599"}

Docs Site Final Structure

Gas Module

dApp Tutorials

CosmWasm Documentation

Bridge Building Strategy

Identify bridge building strategy for archway. i.e which bridge is most feasible to build? Which design is recommended?

1. Prepare for IBC bridge with cosmos-hub (Outcome would be a document answering the following questions and more:)
    - How feasible is it?
    - Can we utilize wasm based light clients?
    - Can we customize ibc integration without forking cosmos-sdk and ibc-go?
    - If the answer to the above question is no, How much effort is it to do this?
2. Prepare for a bridge with eth (Outcome would be a document answering following questions and more:)
    - How feasible is it?
    - Should we go for a trusted or trustless bridge? (Given time constraints)
3. Prepare for bridge with Polkadot parachains (Outcome would be a document answering following 
       questions and more:)
    - How feasible is it?
    - How hard for us to implement a barebone xcmp to allow asset transfer from our blockchain to 
     polkadot

Add gas tracking simulation contracts

We need to start properly testing the environment, so we should create three contracts:

Contract A: calls contract B, performs some state change afterwards.

Contract B: queries (READ ONLY) contract C and applies some state change based on the results returned by C

Contract C: has only a query.

[Economic model] Contract Deployment Strategy

We should define a strategy to deploy contracts.

Archway, compared to wasmd, requires developers to define an address where the network will send rewards to.

This could be done in two ways:

Override the wasmd MsgStoreContract, and enrich it with one extra paramete, the payout_address
Create a two step approach, which means always using wasmd fully but then use a secondary message in the rewards module which binds the contract to an owner. This approach might be more complex (frontrunners of contract creation etc).

Archway daemon is open sourced and:
- Adequate tests (>90% of gastracker code should be covered)
- Comments from developer perspective (Code containing core logic such as custom ante handler, 
  begin block, vm wrapper, custom query handler, custom message handler)
- Add an architecture section in README.md explaining the whole architecture
- Write a paragraph explaining why we designed in this *hacky* way and present upcoming roadmap
- Create issues for the roadmap
- Replace hard coded parameters with governance or genesis configuration
- Document CLI interface of archwayd
- Define versioning scheme and release cycle for archwayd

app/app.go:188:2: `allowedReceivingModAcc` is unused (deadcode)

Go Version: go version go1.16.8 linux/amd64

Maybe we should comment it out if the associated part is not implemented yet.