Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

sendrawtransaction failure reason #116

Closed
enVolt opened this issue Feb 17, 2018 · 5 comments
Closed

sendrawtransaction failure reason #116

enVolt opened this issue Feb 17, 2018 · 5 comments
Labels
enhancement

Comments

@enVolt
Copy link

enVolt commented Feb 17, 2018

I'm signing the transaction using neon-js. When I'm sending the serialized transaction via sendrawtransaction rpc call, it's giving me false result.

Is there any way I can check why the transaction was failed?

Couldn't find anything relevant in the documentation
@enVolt
Copy link
Author

enVolt commented Feb 17, 2018

Update - I've figured out what I was doing wrong. But still, it would be great to have this functionality in neo-cli. Maybe instead of "result": false, it could return some error as why it was failed.

@chrismpalmer
Copy link

I agree with this I am getting a false and have no idea it was just working..

@guotie
Copy link

guotie commented Jun 28, 2018

agreed.

@erikzhang erikzhang mentioned this issue Jun 28, 2018
Merged
@guotie
Copy link

guotie commented Jun 29, 2018

I have the same question, what method did you solve this problem?

erikzhang added a commit to neo-project/neo that referenced this issue Jun 29, 2018
@erikzhang
add failure reason for sendrawtransaction (neo-project/neo-node#116)
852540c
erikzhang added a commit to neo-project/neo that referenced this issue Sep 14, 2018
@erikzhang
refactoring (#288)
c64748e 
* refactoring

* message priority

* add failure reason for `sendrawtransaction` (neo-project/neo-node#116)

* fix bug in `sendrawtransaction`

* improve RpcServer and Plugin system

* add `unconnected` to RPC command `getpeers`

* update dependencies:

- Microsoft.AspNetCore.ResponseCompression v2.1.1
- Microsoft.AspNetCore.Server.Kestrel v2.1.1
- Microsoft.AspNetCore.Server.Kestrel.Https v2.1.1
- Microsoft.EntityFrameworkCore.Sqlite v2.1.1
- Microsoft.Extensions.Configuration.Json v2.1.1

* add WebSocket

* fix bug in Snapshot.Dispose()

* Hides the caught exceptions logs in `RemoteNode`

* fix block stuck

* fix bug in p2p connection

* fix #305

* fix consensus

* checked on Fixed8 mul

* solve the problem of disconnecting from peers

* fix bug in `System.Runtime.GetTime`

* add RPC command: `getwalletheight`

* fix p2p bug

* Prevent error messages when exiting

* optimize p2p network

* allow user interface to send messages to plugins

* change version to 2.9.0

* backward compatible for sendrawtransaction

* Solve the problem of resynchronizing blocks

* put unverified transactions in the memory pool back into the message queue after the block is persisted

* minor change to consensus
@enVolt
Copy link
Author

enVolt commented Sep 15, 2018

I have the same question, what method did you solve this problem?

I was providing the used UTXOs

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@guotie @enVolt @chrismpalmer @erikzhang