Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Dapp deposit fails #51

Closed
TheGoldenEye opened this issue Apr 13, 2016 · 5 comments
Closed

Dapp deposit fails #51

TheGoldenEye opened this issue Apr 13, 2016 · 5 comments
Assignees
Milestone

Comments

@TheGoldenEye
Copy link
Contributor

  • Using Lisk v0.1.4, development branch
  • I created a basic dapp using "lisk-cli dapps -a" without changes
  • starting the node
  • if I try to deposit the dapp using "lisk-cli dapps -d" (here with an amount of 100 LISK), the transaction seems successfull:
$ lisk-cli dapps -d
? Enter secret ****
? Enter amount 10000000000
? DApp Id 16924003274252134805
? Enter secondary secret (if defined) 
? Host and port localhost:7000
null { success: true, transactionId: '13688217344496871545' }
13688217344496871545

The transaction is credited, but seconds later reverted. Only the fee was applied. See screenshot.
image

@karmacoma karmacoma self-assigned this Apr 13, 2016
@karmacoma karmacoma added this to the Mainnet Launch milestone Apr 13, 2016
@TheGoldenEye
Copy link
Contributor Author

In one account the transferred Lisk are credited to the dapp account, but not withdrawn from the sender.
In another account the Lisk are withdrawn, but not credited.
I'll follow it up

@fix
Copy link
Contributor

fix commented May 12, 2016

Hi @TheGoldenEye did you manage to reproduce it with 0.2.x ?

@TheGoldenEye
Copy link
Contributor Author

I just got the dapp running again with 0.2.1.
I will theck the issue this weekend.

@TheGoldenEye
Copy link
Contributor Author

This is an issue of the LiskHQ/lisk-dapps-sdk repo and should be solved there

@TheGoldenEye
Copy link
Contributor Author

beside changes in LiskHQ/lisk-dapps-sdk the issue is LiskHQ/lisk related too

@TheGoldenEye TheGoldenEye reopened this Nov 16, 2016
MaciejBaj added a commit that referenced this issue Apr 10, 2018
Add json schema validation for transaction.signatures property - Closes #51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants