added github actions
This commit is contained in:
parent
556e1231eb
commit
830b51ae8c
|
@ -0,0 +1,36 @@
|
|||
name: Deploy
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- master
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
with:
|
||||
fetch-depth: 0
|
||||
- name: Install mdbook
|
||||
run: |
|
||||
mkdir mdbook
|
||||
curl -sSL https://github.com/rust-lang/mdBook/releases/download/v0.4.15/mdbook-v0.4.15-x86_64-unknown-linux-gnu.tar.gz | tar -xz --directory=./mdbook
|
||||
echo `pwd`/mdbook >> $GITHUB_PATH
|
||||
- name: Deploy GitHub Pages
|
||||
run: |
|
||||
# This assumes your book is in the root of your repository.
|
||||
# Just add a `cd` here if you need to change to another directory.
|
||||
mdbook build
|
||||
git worktree add gh-pages gh-pages
|
||||
git config user.name "Deploy from CI"
|
||||
git config user.email ""
|
||||
cd gh-pages
|
||||
# Delete the ref to avoid keeping history.
|
||||
git update-ref -d refs/heads/gh-pages
|
||||
rm -rf *
|
||||
mv ../book/* .
|
||||
cp ../CNAME .
|
||||
git add .
|
||||
git commit -m "Deploy $GITHUB_SHA to gh-pages"
|
||||
git push --force
|
|
@ -1,4 +1,2 @@
|
|||
.DS_STORE
|
||||
book
|
||||
.github
|
||||
CNAME
|
|
@ -27,7 +27,7 @@ use errors::*;
|
|||
declare_id!("Fg6PaFpoGXkYsidMpWTK6W2BeZ7FEfcYkg476zPFsLnS");
|
||||
|
||||
#[program]
|
||||
pub mod solana_project {
|
||||
pub mod messenger {
|
||||
|
||||
use anchor_lang::solana_program::program::invoke_signed;
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
- [Introduction](./introduction/introduction.md)
|
||||
- [What is an xDapp](./introduction/xdapp.md)
|
||||
- [What is Wormhole]()
|
||||
- [What is Wormhole](./introduction/wormhole.md)
|
||||
- [What is Portal]()
|
||||
- [Wormhole Architecture]()
|
||||
- [Core Bridge Contracts]()
|
||||
|
@ -41,6 +41,7 @@
|
|||
- [Solana]()
|
||||
- [Algorand]()
|
||||
- [Relaying Messages](./development/messages/relaying/overview.md)
|
||||
- [Manual Relays]()
|
||||
- [Rest Relayers]()
|
||||
- [Generic Relayers]()
|
||||
- [Spy Relayer]()
|
||||
|
|
|
@ -0,0 +1,26 @@
|
|||
# What is Wormhole?
|
||||
|
||||
Wormhole is a generic message passing protocol that connects to multiple chains including Ethereum, Solana, Terra, Binance Smart Chain, Polygon, Avalanche, Oasis, and Fantom.
|
||||
Wormhole does this through emitting messages from one chain which are observed by a Guardian network of nodes and verified. After verification, this message is submitted to the target chain for processing.
|
||||
This simple message passing primitive enables cross chain functionality. Users interact with xDapps (cross chain decentralized applications) to transfer xAssets (cross chain assets) between networks or access their xData (cross chain data) to provide them services on their current network.
|
||||
On top of the Wormhole message protocol, there’s two specific applications that help concentrate liquidity for xAssets. The Portal Token Bridge and Portal NFT Bridge provide a standard message format for token and NFT transfers across the Wormhole bridge.
|
||||
|
||||
## What can Wormhole be used for?
|
||||
Wormhole can be used by developers to build xDapps, a new type of chain agnostic application that can take advantage of xAssets and xData. This allows for access to increased liquidity, communities, and user identity.
|
||||
|
||||
Some prominent examples of xDapps:
|
||||
|
||||
- Cross chain exchange:
|
||||
|
||||
Using Portal, the Token Bridge built on Wormhole, a developer can build an exchange that allows deposits from any Wormhole connected chain, massively increasing the liquidity their users can interact with. A user could directly deposit LUNA from Terra into an app running on Solana! All the developer has to do is integrate Wormhole SDK into their frontend and that deposit will get picked up by the Portal Token Bridge, and taken over to target chain.
|
||||
|
||||
- Cross chain governance app:
|
||||
|
||||
Consider all the NFT collections on various networks. If a group of these collections on different networks wanted their holders to vote on a combined proposal, they could pick a “Voting” chain, and use Wormhole to shuttle all the votes from cast on their various chains to the voting chain.
|
||||
|
||||
- Cross chain game:
|
||||
|
||||
A game could be built and played on a performant network like Solana, and it’s rewards issued as NFTs on a different network, for example Ethereum.
|
||||
|
||||
## How does Wormhole work?
|
||||
Wormhole has a Core Bridge contract deployed on all the connected networks. Wormhole Guardians run a full node for each of the connected chains, specifically listening to any events from the Core Contracts. The core contracts emit a message, which is picked up by the Guardians. The Guardians verify the message and sign it, creating a VAA (Verified Action Approval). This VAA then sits on the Guardians network where it can be retrieved by the user or by a relayer to be submitted to the target chain to process the message. Unlike other bridges, a relayer in Wormhole has no special privileges, it’s just a piece of software that shuttles messages between the Guardian network to the target chain, and is not a trusted entity.
|
|
@ -0,0 +1,2 @@
|
|||
# Messenger
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
# Messenger Preqs
|
||||
|
||||
|
||||
## EVM
|
||||
- Foundry
|
||||
|
||||
## Algorand
|
||||
- Python3
|
||||
- pip3 install -r requirements.txt
|
||||
|
||||
## Solana
|
||||
- Rust
|
||||
- Anchor > 0.24.0
|
||||
- Solana Cli > 1.9.14
|
|
@ -0,0 +1,5 @@
|
|||
# Projects
|
||||
|
||||
## xDapp Starter
|
||||
|
||||
## Messenger
|
Loading…
Reference in New Issue