An open API service indexing awesome lists of open source software.

https://github.com/syscoin/sysethereum-dapp

Reference UI for the Syscoin <=> Ethereum bridge
https://github.com/syscoin/sysethereum-dapp

bitcoin cryptocurrency ethereum highspeedassets sidechain spvbridge syscoin

Last synced: 9 months ago
JSON representation

Reference UI for the Syscoin <=> Ethereum bridge

Awesome Lists containing this project

README

          

![Preview](./home.png)
## Sysethereum DAPP
This is a reference implementation of a user interface showcasing the Syscoin <=> NEVM bridge. It will create a SPV proof of Syscoin burn transactions post to the relay smart contract which will validate and call a Token contract which uses ERC20Manager to transfer from and to.

On the way back to Syscoin. An SPV proof of the NEVM transaction is created using [eth-proof](http://github.com/syscoin/eth-proof) and will call a burn function from the ERC20Manager base of the Syscoin Token contract that holds the tokens. It's purpose is to store and transfer tokens and the function parameters are used via ABI data to detect the value of the burn once Syscoin consensus reads the transaction data.

Syscoin itself enforces the SPV proof by running Geth in light mode to sync up to the last few weeks of headers on NEVM. Syscoin nodes run a custom version of Geth which validates NEVM blocks and speaks to Syscoin over ZMQ socket transport layer. The Transaction root is queried for when a Syscoin mint transaction is created (when NEVM contract burns Syscoin tokens on the ERC contract). The calculated Transaction Root must match the Transaction Root saved in the database which validates that the NEVM transaction was valid and subsequently minting new Syscoin or Syscoin assets into existence. The total supply of Syscoin/Syscoin assets should remain constant throughout the process as the bridge represents a zero-sum game.
## Dependencies

1) Just Pali chrome extension wallet and Metamask!
2) You should configure `config.js` to point to your Web3 setup and explorer links if you are testing on a different network.

## Available Scripts

In the project directory, you can run:

### `npm install`
Installs the dependencies. You should use node version 16.

### `npm start`

Runs the app in the development mode.

Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.

You will also see any lint errors in the console.

set REACT_APP_USE_TESTNET=true in your env for testnet.
### `npm test`

Launches the test runner in the interactive watch mode.

See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `npm run build`

Builds the app for production to the `build` folder.

It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.

Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `npm run build` fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify