• improve the contract so that you don't have to send your username as param, we want to get that from the EOS account that's signing the contract.
• add ricardian clauses

I'm not used to TypeScript, I understand the benefits, however most TypeScript code I see looks a bit alien to me, people tend to write object oriented code when using typescript.

The Demux service we currently have inherited code style from MonsterEOS.

I want to open up the discussion for this.

Personally, I'm fine without TypeScript.

https://github.com/eoscostarica/eos-dapp-boilerplate/blob/master/scripts/deploy-contracts.sh

Summary

Getting started documentation is poor. It is not immediately obvious you need to run cd services/frontend && yarn && cd ../../ && make start instead of make start.

Steps to reproduce: How did you encounter the bug? Instructions to reproduce it.

Clone the project. Run make start.

Expected behavior: How did you expect it to behave?

It would fire up the app without problems

Actual behavior: How did it actually behave?

Complained that rimraf could not be found, which is obviously due to the node_modules folder being missing.

Possible Solutions

Changing the make start command to this cd services/frontend && yarn && cd ../../ && ./scripts/start.sh would be more appropiate.

Docs
https://developers.eoslynx.com/

Telegram
https://t.me/lynxapps

As first step make sure you can read the account name from the wallet API.

It seems we could handle postgres migration with Hasura.
https://docs.hasura.io/1.0/graphql/manual/migrations/index.html

Currently we use flywaydb for that.

https://reactjs.org/docs/hooks-intro.html

document when to use and to choose between jsonb documents and tables.

IMO we should support both JavaScript Testing and C++ testing

reference
https://truffleframework.com/docs/truffle/testing/writing-tests-in-javascript

https://docs.hasura.io/1.0/graphql/manual/deployment/index.html

1. Configure your Local Network in Scatter

2. Configure your Scatter with the Testing Users created on the init script see
   https://github.com/eoscostarica/eos-local/blob/master/services/eos-dev/scripts/0000_init-chain.sh

3. Stake some tokens for RAM and CPU

This step won't be necessary when eoscostarica/eos-local#40 is completed.

4. Make sure you sign messages using Scatter on the EOS Greeting reactjs demo client. Update client side code as required.

API Integration Testing, Black Box Non-Regression

• deploy contract to the Jungle Testnet