Closed ceecko closed 2 years ago
The same behavior is with API v3.
Sending params such as the following uses just the first utxo1
[
{
fee: '10000',
mychange: 'address',
receivers: 'address:30000',
type: 0,
utxos: [
'utxo1:0',
'utxo2:0',
'utxo3:0'
]
}
]
Is there any error msg return? Try to change the type field
The error message is, there is not enough unspent funds for the transaction.
The unspent amount equals to the first utxo1:0
that's why I assume it's using just the first one.
What would you suggest for the type field? I'd like to transfer ETP which shall be type 0
if I understand the docs correctly
@ceecko fixed. Thanks for your reporting this issue.
@betachen Thanks. The latest commit fails to build via Dockerfile. Is this expected?
> [7/8] RUN cd /tmp/metaverse && mkdir -p build && cd build && cmake .. && make -j2 && make install && rm -rf /tmp/metaverse/build && rm -rf /tmp/metaverse/build-mvs-dependencies:
#12 0.550 -- The C compiler identification is GNU 5.4.0
#12 0.592 -- The CXX compiler identification is GNU 5.4.0
#12 0.598 -- Check for working C compiler: /usr/bin/cc
#12 0.627 -- Check for working C compiler: /usr/bin/cc -- works
#12 0.628 -- Detecting C compiler ABI info
#12 0.658 -- Detecting C compiler ABI info - done
#12 0.664 -- Detecting C compile features
#12 0.752 -- Detecting C compile features - done
#12 0.755 -- Check for working CXX compiler: /usr/bin/c++
#12 0.791 -- Check for working CXX compiler: /usr/bin/c++ -- works
#12 0.791 -- Detecting CXX compiler ABI info
#12 0.827 -- Detecting CXX compiler ABI info - done
#12 0.833 -- Detecting CXX compile features
#12 1.000 -- Detecting CXX compile features - done
#12 1.130 Boost 1.56 found.
#12 1.130 Found Boost components:
#12 1.130 date_time;filesystem;system;program_options;regex;thread
#12 1.130 CMake Error in /opt/cmake/share/cmake-3.9/Modules/FindBoost.cmake:
#12 1.130 cmake_policy PUSH without matching POP
#12 1.130 Call Stack (most recent call first):
#12 1.130 CMakeLists.txt:95 (FIND_PACKAGE)
#12 1.130
#12 1.130
#12 1.131 -- Found secp256k1: /usr/local/lib/libsecp256k1.so
#12 1.133 -- ZeroMQ version: 4.2.1
#12 1.134 -- Found ZeroMQ: /usr/local/include (found suitable version "4.2.1", minimum required is "4.2.0")
#12 1.143 -- CryptoPP not found, use existed implementation
#12 1.148 -- Looking for byteswap.h
#12 1.176 -- Looking for byteswap.h - found
#12 1.177 -- Looking for endian.h
#12 1.205 -- Looking for endian.h - found
#12 1.216 -- Configuring incomplete, errors occurred!
#12 1.216 See also "/tmp/metaverse/build/CMakeFiles/CMakeOutput.log".
#12 1.216 See also "/tmp/metaverse/build/CMakeFiles/CMakeError.log".
------
executor failed running [/bin/sh -c cd /tmp/metaverse && mkdir -p build && cd build && cmake .. && make -j2 && make install && rm -rf /tmp/metaverse/build && rm -rf /tmp/metaverse/build-mvs-dependencies]: exit code: 1
@ceecko please try the latest version Dockerfile from the docker directory. if it does not work please create a new issue
@canguruhh works like a charm, thank you When do you expect to release a new version with this fix included?
What would be the correct format when using
createrawtx
to specify multiple utxos to be used via--utxos
?I tried the following, but none work
--utxos
argumentsI'm using the API v1 on
/rpc
endpoint and it seems to support a single--utxos
parameter.