search

sumoprojects / sumokoin

Sumokoin - Digital Cash For Highly-Confidential Transactions
https://www.sumokoin.org
Other
131 stars 69 forks source link

transaction was not constructed #118

Closed minerrocks closed 6 years ago

minerrocks commented 6 years ago

Unlocked first block on pool, and payment cannot be done with transfer_split. It seems that monero-project already has a fix for transaction was not constructed, can you check?

As can be seen from wallet-rpc log - there are no integrated (Sumi) or subaddresses (Subo) involved, only main account addresses (Sumo).

2018-Apr-16 20:44:32.063702 [RPC0]ERROR /home/sumocoin/sumokoin/src/wallet/wallet2.cpp:695 Unsupported rct type:  
2018-Apr-16 20:44:32.069809 [RPC0]Received money: 36.450000000, with tx: <ed66109526ad4c52ee6e87316fb315ee35679e8ad4134fb17302a504d92d4aaf>
2018-Apr-17 01:56:31.609822 [RPC0]selected transfers: 
2018-Apr-17 01:56:31.735975 [RPC0]amount=36.450000000, real_output=10, real_output_in_tx_index=0, indexes: 652827 963990 984371 1066706 1116930 1141570 1142614 1142890 1143868 1144865 1147135 1148016 1148176 
2018-Apr-17 01:56:31.736098 [RPC0]ERROR /home/sumocoin/sumokoin/src/cryptonote_core/cryptonote_format_utils.cpp:602 Destinations have to have exactly one output to support encrypted payment ids
2018-Apr-17 01:56:31.736495 [RPC0]ERROR /home/sumocoin/sumokoin/src/wallet/wallet2.cpp:4057 !r. THROW EXCEPTION: error::tx_not_constructed
2018-Apr-17 01:56:31.736922 [RPC0]/home/sumocoin/sumokoin/src/wallet/wallet2.cpp:4057:N5tools5error18tx_not_constructedE: transaction was not constructed
Sources:
  source 0:
    amount: 36.450000000
Destinations:
  0: Sumoo2yEu... 4.120000000
  1: Sumoo2guZ... 1.430000000
unlock_time: 0
2018-Apr-17 01:56:35.867626 [RPC0]ERROR /home/sumocoin/sumokoin/src/wallet/wallet2.cpp:695 Unsupported rct type:  
2018-Apr-17 01:56:35.868098 [RPC0]Received money: 36.450000000, with tx: <ed66109526ad4c52ee6e87316fb315ee35679e8ad4134fb17302a504d92d4aaf>
quangvu3 commented 6 years ago

From the error:

Destinations have to have exactly one output to support encrypted payment ids

So, payment id cannot be used for tx with multiple destinations. The error reporting should be better though.

minerrocks commented 6 years ago

sorry, i have found from pool logs that integrated address passed to wallet-rpc with non-integrated address at the same time.

Issue closed.