Go to http://stage.loomx.io/developers/en/cocos-sdk-quickstart.html#install-loom

Incorrect Favicon page https://loomx.io/developers/en/prereqs.html

Video: https://slack-files.com/T7AB1S3LN-FK0PSSJFP-be243bd6b6

https://slack-files.com/T7AB1S3LN-FJL5A8L81-af451456dd

Add stable builds of loom to the docs site

Based on the e2e tests

We have a previous ticket for this - #184

Not sure if this was fixed but let's take a look at it and if not we should get this in to-do. The previous issue is closed so I created this new one for tracking.

According to a comment from SORARE - still the addresses have issues ->

Preview

Pierre, [19.06.19 16:18]
hello. can you confirm that the ethereum transfer gateway address is 0x223CA78df868367D214b444d561B9123c018963A ?

Pierre, [19.06.19 16:18]
I'm starting the tests on mainnet

Pierre, [19.06.19 16:19]
it is the address I found here: https://loomx.io/developers/docs/en/testnet-plasma.html#contract-addresses-transfer-gateway

Pierre, [19.06.19 16:19]
but looks like the last tx was 90 days ago

Nayeem | Loom Network, [19.06.19 16:21]
[In reply to Pierre]
hey checking sec

Pierre, [19.06.19 16:21]
seems like the right address is 0xE080079Ac12521D57573f39543e1725EA3E16DcC

Pierre, [19.06.19 16:21]
you should update your website

Matthew Campbell, [19.06.19 16:22]
@nayeemsidd can you add a ticket on the docs site and get andrei to fix this

Update the docs to let people know how to tweak the default timeouts.

Document querying our event store and setting up one

On the page to install the Loom SDK the first step results in a 404:
curl https://raw.githubusercontent.com/loomnetwork/loom-sdk-documentation/master/scripts/get_loom.sh | sh

sh: 1: 404:: not found

Explain how a user can deploy its own node and connect for reads to extdev.

put the JSON file and a markdown version into docs

The updated dashboard/wallet going out this week has better ui for mainnet key generation. Lets have a walkthrough on how to use it

https://fortmatic.com

Add mossland project using Loom SDK in help page.

Your medium posting is here

Mossland project url is here.

URL: http://stage.loomx.io/developers/en/docker-blueprint-phaser.html#phaser-sdk-demo

Replace old join testnets page with the new one

TypeError returned when I issued "node ./gateway-cli.js map-contracts token". I changed rinkeby API key in the gateway-cli.js.

TypeError: callback is not a function at LoomProvider.<anonymous> (/home/ether/work/truffle/truffle-dappchain-example/node_modules/loom-js/dist/loom-provider.js:257:25) at step (/home/ether/work/truffle/truffle-dappchain-example/node_modules/tslib/tslib.js:133:27) at Object.next (/home/ether/work/truffle/truffle-dappchain-example/node_modules/tslib/tslib.js:114:57) at /home/ether/work/truffle/truffle-dappchain-example/node_modules/tslib/tslib.js:107:75 at new Promise (<anonymous>) at Object.__awaiter (/home/ether/work/truffle/truffle-dappchain-example/node_modules/tslib/tslib.js:103:16) at LoomProvider.send (/home/ether/work/truffle/truffle-dappchain-example/node_modules/loom-js/dist/loom-provider.js:227:24) at VersionMethod._callee$ (/home/ether/work/truffle/truffle-dappchain-example/node_modules/web3/node_modules/web3-core-method/dist/web3-core-method.cjs.js:454:55) at tryCatch (/home/ether/work/truffle/truffle-dappchain-example/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40) at Generator.invoke [as _invoke] (/home/ether/work/truffle/truffle-dappchain-example/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:288:22) at Generator.prototype.(anonymous function) [as next] (/home/ether/work/truffle/truffle-dappchain-example/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21) at asyncGeneratorStep (/home/ether/work/truffle/truffle-dappchain-example/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24) at _next (/home/ether/work/truffle/truffle-dappchain-example/node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9) at /home/ether/work/truffle/truffle-dappchain-example/node_modules/@babel/runtime/helpers/asyncToGenerator.js:32:7 at new Promise (<anonymous>) at VersionMethod.<anonymous> (/home/ether/work/truffle/truffle-dappchain-example/node_modules/@babel/runtime/helpers/asyncToGenerator.js:21:12) at VersionMethod.execute (/home/ether/work/truffle/truffle-dappchain-example/node_modules/web3/node_modules/web3-core-method/dist/web3-core-method.cjs.js:477:25) at Proxy.anonymousFunction (/home/ether/work/truffle/truffle-dappchain-example/node_modules/web3/node_modules/web3-core-method/dist/web3-core-method.cjs.js:228:25) at Command.<anonymous> (/home/ether/work/truffle/truffle-dappchain-example/gateway-cli.js:899:59) at process._tickCallback (internal/process/next_tick.js:68:7)

Here's npm package versions.
@babel/[email protected]
@babel/[email protected]
@babel/[email protected]
@babel/[email protected]
@babel/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

The docs from the Multi-node deployment section from the SDK documentation says that you need to let your node learn about other peers on the network by running

loom run <peer-list>

However the CLI help command for loom run --help says that it should be

loom run -p <peers>

I have tested both ways of setting things up and can confirm the sdk-docs are incorrect. It only works with the -p option.

https://loomx.io/developers/en/delegated-proof-of-stake.html

Note: These buttons are working on Android devices

Video link: https://slack-files.com/T7AB1S3LN-FJUK909NJ-c883bb6cb7

List and explain a bit the events emitted by the transfer gateway.

Refer to the #129.
And also, Word in diagrams is needed to fix like below.
I can not modify that.

In Loom global structure diagram,

• CocosProtingLayer => CocosPortingLayer (O)

In Loom Cocos SDK structure diagram

• Cocos Proting Layer => Cocos Porting Layer (O)

On the "Building DAppChain clients in Golang" page (go-loom-clients), the documentation currently indicates:

In this section you'll be introduced to the go-loom API that you will use to write Go code that interacts with a Loom DAppChain, writing smart contracts in Go will be covered in a later section.

That "writing smart contracts in Go" bit I can't find in the existing documentation. Does it exist or need to be created yet? The helloworld sample contract written in Go has some examples of needed syntax, but the deployment and other nuances of a Go contract don't seem to be covered.

content is out of date and not useful

Need a list of steps and background about nonce issues and why resending the same data to the Blockchain won’t work.

These addresses are outdated: https://loomx.io/developers/docs/en/testnet-plasma.html

Should have some basic docs on how to bootstrap ethers on loom
Also how to use Eth signing

URL: http://stage.loomx.io/developers/en/etherboy-game.html#game-controls

Broken Url: http://stage.loomx.io/developers/en/unity-sdk.html

Video:

Pretty sure these are all outdated and not maintained

Try using portis as the web3 provider

https://github.com/portis-project/web-sdk/blob/master/packages/portis-web3/src/index.ts#L262

if it works, add a new doc page for it

put some samples showing how to run golang contracts like address_mapper against localhost

We need a doc that does the following.

1. Has a single git repo, with an erc20 token.
2. Truffle deploy steps
   a) Mainnet Ethereum
   b) Mainnet Loom Chain

Lets try and reuse this https://github.com/loomnetwork/truffle-dappchain-example

3. Has directions on how to mint a new token on Binance Testnet ( Talk to deeprom on steps for this)
4. Has how to link to transfer gateways, to evm contract on loom
   a) on Eth
   b) on Binance
5. Walks user how they can move tokens through all three chains
6. Lets update the token to also have mintable/burnable functions on mainnet, for tokens that have inflationationary supply

in this page : https://loomx.io/developers/docs/en/web3js-loom-provider-truffle.html. In the Overview, The link for EVM page is 404.
it should be https://loomx.io/developers/docs/en/evm.html
white it is https://loomx.io/developers/docs/en/docs/en/evm.html now, with an extra docs/en/

Steps:

1, Go to http://stage.loomx.io/developers
2, Hover the mouse on Right side of the page and use mouse scroller, It worked
3, Hover the mouse on sidebar and try to use mouse scroller, It didn't worked smoothly instead it tries to scroll the right side of the page

Video Ref: https://screenpresso.com/=BWGTe

Genesis files are not meant to be edited after the boot of the chain. We should probably note that, for people experimenting.

Favicon url: http://stage.loomx.io/developers/img/favicon/favicon.ico

Note: This screen show is from Chrome/Desktop

Screen shot from iPhone

In docs/phaser-sdk-demo-websocket-web3.md and website/translated_docs/zh-CN/phaser-sdk-demo-websocket-web3.md

to create seamlessly experience

should be

to create seamless experiences

or

to create a seamless experience

Video Ref: https://slack-files.com/T7AB1S3LN-FJF3BL4E7-644fc7c253

Dear @mattkanwisher,

Every new release, you need to change download url for loom binary in all repository’s readme file and dev page.

It is not comfortable to maintain, so I suggest that you’d better get a url always pointing to latest version of loom like below.

(example)
https://private.delegatecall.com/loom/osx/build-latest/loom

is now exactly same as

https://private.delegatecall.com/loom/osx/build-404/loom.

This make it easier to download latest version of loom any time and reduce useless commits to change version of loom, less conflicts for developer.

Thanks

There's a small bug in the developer documentation site. Once I click on the Docs under Loom SDK product page, the docs page opens without the side navigation bar. I have to click on "Docs" at the top to see the navigation bar.

Draft:
We go here, https://dev-dashboard.dappchains.com/add-key. first, you will click on generate a new public address. then, you will copy and paste the mnemonic and the public address. put the mnemonic somewhere safe. paste the address and click add key. you will be asked to stake (or pay?) some amount of loom (10?). lastly, you’ll use the mnemonic to deploy with truffle. i’m going to show them how to add the mnemonic to truffle-config.js.