Gridcoin-research: listsinceblock and listtransactions don't show incoming unconfirmed transactions

[santins77]

The list of transactions returned by listsinceblock and listtransactions don't show the incoming transactions with 0 confirmations. They are only shown when they reach one confirmation. This rpc api behavior is different comparing to bitcoin and some other bitcoin family coins

[iFoggz]

the listtransactions functionality is not much different then bitcoins actually . if the transaction has 0 confirms it does show for me in listtransactions with 0 confirms (sent to myself). default it shows only 10 transactions. there are some issues regarding listsinceblock in the main release that is addressed in development slated for release in near future.i'll verify there were no changes to listtransactions since release

only time no tx would be shown is if it conflicted -1

also note that if someone sends u a tx u wont see it till 1 confirm anyway as the block u receive that has the tx is considered first confirm

[santins77]

I'm having the issue when the transaction is sent from some external address to my wallet. When I sent money from my wallet to another address the commands seem to work OK. That is why I mention in incoming transactions.

[iFoggz]

so your sending from a wallet to another wallet then? or are you sending between two addresses within same wallet?

[iFoggz]

any txs received from the network from two different wallets wont show till 1 confirm as it sits in the memory pool until a staked block carries the transaction

[santins77]

Do you have in mind to change that behavior? In bitcoin, lite, and others the show this transactions in those cases

[iFoggz]

that would likely occur when we do a rebase to add the functionality of showing transactions sitting in the memory pool.

[iFoggz]

we will be re-basing to update the long overdue code in the files

[santins77]

OK. Nice! Thanks for the info

[iFoggz]

getrawmempool rpc command will display all txs in the memory pool waiting to be staked in a block. you can still gettransaction a tx if it is in the memorypool