Local daemon crashes when sending transaction with mixin over 0

[frankiexile]

Assertion failed: ofa.outs.size() && "internal error: ofa.outs.size() is empty", file C:\Paradigm\src\Rpc\RpcServer.cpp, line 270

[frankiexile]

does anyone have a solution for this? im just trying to test transactions and i can't figure out where this error is coming from

[frankiexile]

the only thing i can think of is when i changed the CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE to 1000000 to increase the max transaction size because i couldnt send more than 500000 coins at a time. dont know if this has anything to do with it but if it does what is the proper way to increase the max tx size

[SoraKohaku]

on max trans size already just make fee balance

On Thu, May 24, 2018, 6:14 AM frankiexile notifications@github.com wrote:

the only thing i can think of is when i changed the CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE to 1000000 to increase the max transaction size because i couldnt send more than 500000 coins at a time. dont know if this has anything to do with it but if it does what is the proper way to increase the max tx size

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/264#issuecomment-391498617, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tYomXugki1P9m-37BV6JlnS1McvRks5t1dE-gaJpZM4UJUkr .

[frankiexile]

are you saying that i need to make the minimum fee higher?

[SoraKohaku]

yep cuz if over balance of transaction will become orphan block

On Thu, May 24, 2018, 10:30 AM frankiexile notifications@github.com wrote:

are you saying that i need to make the minimum fee higher?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/264#issuecomment-391558624, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tXSIhRccORn7YNhkLl1J7Zlsw2ytks5t1g1NgaJpZM4UJUkr .

[frankiexile]

ok so CRYPTONOTE_MAX_TX_SIZE = 1000000000;

does that mean that minimum fee needs to be = 1000000000; as well?

[frankiexile]

block granted full reward = 100000 also

[frankiexile]

after doing some tests i think this issue was linked to having 2 wallets on the same machine running on the same local daemon. when i sent from wallet 1 to wallet 2 everything was fine, then i sent from wallet 2 back to wallet 1 with a mixin of over 0 and i get this crash error. then it doesnt allow me to send with a mixin over 0 from wallet 1 anywhere either. only until after i deleted wallet 2 off this machine and sent money to a wallet on a completely different computer the issue completely went away as far as i know.

[SoraKohaku]

no used for 2 wallet you need 1 wallet 1 machine and many adress accept that rule of decentralize. 1 app 1 options. but heavy and Cn-7 difficulty is great even processor is hardening. just GPU is fast. need clarify again for this~between CPU for old times fast now they priority GPU Heavy, Lite and CN-7 PoW.

try look my repo v3 if interested on CN-7. for heavy is V2. we not sure what we follow for prevent or accept asic who know. just inform...

fee no need

[SoraKohaku]

why you need 1 machine 2 wallet. used lite bro with python programs

On Sat, May 26, 2018, 8:19 AM frankiexile notifications@github.com wrote:

after doing some tests i think this issue was linked to having 2 wallets on the same machine running on the same local daemon. when i sent from wallet 1 to wallet 2 everything was fine, then i sent from wallet 2 back to wallet 1 with a mixin of over 0 and i get this crash error. then it doesnt allow me to send with a mixin over 0 from wallet 1 anywhere either. only until after i deleted wallet 2 off this machine and sent money to a wallet on a completely different computer the issue completely went away as far as i know.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/264#issuecomment-392211689, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tStVuqbETp-eJZe4jRW8cth6MaNEks5t2JF-gaJpZM4UJUkr .