Update README

This commit is contained in:
emizzle 2019-06-26 13:11:53 +10:00
parent dc50751f20
commit 39ac96252d
No known key found for this signature in database
GPG Key ID: 1FD4BAB3C37EE9BA
1 changed files with 1 additions and 1 deletions

View File

@ -20,7 +20,7 @@ Please see [`embark-plasma`](https://github.com/embark-framework/embark-plasma)
## Current limitations and known issues ## Current limitations and known issues
1. The plugin currently only supports OMG's Samrong network and `v0.2` of the OMG SDK. The root chain is a contract on Rinkeby and the Plasma chain runs on Samrong. Chain creation for development purposes will be added in future versions. 1. The plugin currently only supports OMG's Samrong network and `v0.2` of the OMG SDK. The root chain is a contract on Rinkeby and the Plasma chain runs on Samrong. Chain creation for development purposes will be added in future versions.
2. The DApp must use Metamask. The accounts configured in the blockchain config cannot be used in the DApp. This is a limitation of Embark itself, and will hopefully be updated soon. 2. The DApp can use Metamask OR accounts configured in the contracts config of Embark. Due to this support, the private keys of the accounts configured in Embark will be passed to `EmbarkJS.Plasma` and will be visible in the code generated `embarkjs.js` file. We are hoping to remove the need to pass PK's around soon.
## Available properties/functions ## Available properties/functions
`embarkjs-plasma` exposes functions that are meant to make DApp interaction with Plasma chains easier. The following functions and proeprties are available. `embarkjs-plasma` exposes functions that are meant to make DApp interaction with Plasma chains easier. The following functions and proeprties are available.