There are developer tools that help you develop, test, and deploy dapps in a way that automatically utilizes the resources listed below.
Solidity Docs – Solidity is the Expanse developed Smart Contract language, which compiles to EVM (Expanse Virtual Machine) opcodes.
Test Networks – Test networks help developers develop and test Expanse code and network interactions without spending their own Expanse on the main network. Test network options are listed below.
Dapp development resources. This assists you in developing, debugging, and deploying Expanse applications.
Mix is the official Expanse IDE that allows developers to build and deploy contracts and decentralized applications on top of the Expanse blockchain. It includes a Solidity source code debugger. Mix
Below are developer frameworks and IDEs used for writing Expanse dapps.
Truffle – Truffle is a development environment, testing framework and asset pipeline for Expanse.
Dapple – Dapple is a tool for Solidity developers to help build and manage complex contract systems on Expanse-like blockchains.
Populus – Populus is a Smart Contract development framework written in python.
Eris-PM – The Eris Package Manager deploys and tests smart contract systems on private and public chains.
Commandline console for Expanse nodes.
Here you could find a list of available commands expanse node control commands
To use this console you would need to start a local expanse node with ipc communication socket enabled (file gexp.ipc in data directory). By default ipc socket should be located at you local home directory in .expanse after you started a node. You could also set –test option to use specific node test commands.
In the console you could then type
Here the defenition of –test mode node commands:
More information about node configuration file.
What is Whisper and what is it used for – stackexchange Q&A
Gavin Wood: Shh! Whisper – DEVCON-1 talk youtube video
Swarm is a distributed storage platform and content distribution service, a native base layer service of the Expanse web 3 stack. The primary objective of Swarm is to provide a sufficiently decentralized and redundant store of Expanse’s public record, in particular to store and distribute dapp code and data as well as block chain data. From an economic point of view, it allows participants to efficiently pool their storage and bandwidth resources in order to provide the aforementioned services to all participants.
From the end user’s perspective, Swarm is not that different from WWW, except that uploads are not to a specific server. The objective is to peer-to-peer storage and serving solution that is DDOS-resistant, zero-downtime, fault-tolerant and censorship-resistant as well as self-sustaining due to a built-in incentive system which uses peer to peer accounting and allows trading resources for payment. Swarm is designed to deeply integrate with the devp2p multiprotocol network layer of Expanse as well as with the Expanse blockchain for domain name resolution, service payments and content availability insurance.
ÐΞVcon talks on swarm
Viktor Trón, Daniel A. Nagy: Swarm – Expanse ÐΞVcon-1 talk on youtube
Daniel A. Nagy: Keeping the Public Record Safe and Accessible – Expanse ÐΞVcon-0 talk on youtube
Code and status
[issues on github](https://github.com/expanse-org/go-expanse/labels/swarm)
Storage on and offchain
What is swarm and what is it used for? – stackexchange Q&A
Decentralized cron service in Expanse proposal – by Peter Szilagyi
Author: Piper Merriam
A marketplace that facilitates verifiable execution of computations off-chain. Allows for very expernsive computations to be used within the EVM without having to actually pay the high gas costs of executing them on-chain.
More information (about ETH/BTC 2-way peg without modifying bitcoin code).
The Expanse Virtual Machine (EVM) is the runtime environment for smart contracts in Expanse. It is not only sandboxed, but actually completely isolated, which means that code running inside the EVM has no access to network, filesystem, or other processes. Smart contracts even have limited access to other smart contracts.
Contracts live on the blockchain in an Expanse-specific binary format (EVM bytecode). However, contracts are typically written in an Expanse high level language, compiled into byte code using an EVM compiler, and finally uploaded on the blockchain using an Expanse client.