Lucio M. Tato

Hi! @vgrichina, @MaxGraey Regarding functionality required by NEAR, I'm creating the AssemblyScript version of one of the core contracts: staking-pool. In order to complete the task, I need to be...

It is "jump-table"

**Idea**: Considering that NEAR accountIds are human-readable, not just addresses, the NEAR exchanges could use the depositor's accountId as user name, then the hot-wallet deposit & account creation becomes a...

I dived into `near-cli call` code and as far as I can see, the params must be JSON, must be an object, and the JSON gets converted into values for...

Try indenting 4 spaces the line. code is always indented at least 4 spaces. (Note: ''' won't do). ``` $ echo " print 'hi'">test.lite $ lite -v 0 -run test.lite...

I'm sorry for that. The nice+parallel example got neglected while I was focusing on the compile-to-c feature. **_Now the example is fixed, please try it**_ Thanks for the detailed report....

Maybe the error message should be "called twice/wait.for inside async fn" If you think about it, It does not make sense to call wait.for inside an "async" fn (a fn...

we're minting tokens for the user, can you add `ft_mint_to` to the possible fn names? ``` const received = select distinct receipt_receiver_account_id as receiver_account_id from action_receipt_actions where args->'args_json'->>'receiver_id' = $1...

Great! `DeleteState` will be very useful during development too! I'll edit the issue title to reflect what you're saying