sygna-bridge-api v1.1.0

If there is a new exchange want to join sygna-bridge ecosystem. These steps need to be followed. 1. The exchange need to give us their vasp_pubkey,vasp_receive_url(used in beneficiary role). 2. We need to generate vasp_api_key by sha256 function for the exchange to authorize. 3. Make sure their firewall rule could accept the request from dynamic IP.If they block please set the is_sb_need_static_ip column's value to true and we would request their server via static IP.If the is_sb_need_static_ip column's value is false means we would request their server from lambda function(dynamic IP) not EC2 server(static IP)). 4. We need to give them the public key that use to verify the signature of the vasp_data(/vasp). 5. We need to give them the public key that use to verify the signature of the transfer status response(/transaction/status).

Notice

1. We didn't have a decision about how to give public key or something to the exchange.
2. Now the two util lambda timeout sec is 59s,please notice the timeout sec of calling 3rd party server is totally 30s.If you change one timeout sec you need to make sure the other is fine.

ENV

NODE_ENV=
AWS_DYNAMO_ACCESS_KEY_ID=
AWS_DYNAMO_SECRET_ACCESS_KEY=
AWS_DYNAMO_REGION=
TABLE_VASP=
TABLE_TRANSFER=
TABLE_VASP_AUTH=
TABLE_RETRY_TRANSFER_TASK= TABLE_VASP_SIG= VASP_INFO_SIGNATURE=
SB_API_PRIVATE_KEY=
AWS_SQS_URL=
AWS_SQS_REGION=
SB_API_KEY=