fullnode down…
(Outdated post) Network Explorer
1 Like
Not sure why, maybe Incognito Team removed some of the fixed nodes.
1 Like
We’re back.
@Mike_Wagner Validators count is rebuilding from scratch, we’ll see if that fixes the issue or not.
I fixed another thing about new BSC tokens, it seems Incognito Team decided to replace tokens on https://api.incognito.org/ptoken/list endpoint, so new tokens were not indexed… For Incognito Team: Idk why you decided to add BNB_BSC as the token with id 5 but that’s weird.
2 Likes
And here I thought Incscan had become prescient and was now predicting the number of nodes to be unstaked in the future, lol.
FWIW – still shows as negative.
1 Like
There is a problem but I cannot determine what it is. I think the problem is on the blockchain side but I’m not sure. I check regularly for many hours. mempool page of incscan is empty but when I send mempool RPCs to mainnet and community fullnodes , there are always some transactions pending Txs in mempool. Then I check lock time of some of them and they are way behind the actual time. What’s happening exactly? 
Thanks.
1 Like
I think I read somewhere that they changed something about mempool, but not sure.
And the mempool here https://mainnet.incognito.org/txs/pending is quite weird, 700+ txs, yeah.
No idea 
3 Likes
Mempool is back: https://incscan.io/blockchain/mempool
getrawmempool rpc method doesn’t seem to work anymore.
2 Likes
(From Network Explorer)
Hey @inccry,
In case you miss the change, PrivacyCustomTokenProofDetail > OutputCoins > Value is the new place of the exact buy amount. Currently, incscan shows minacceptablevalue (which is fallback option I think) as the buy amount.
Best.
1 Like
Hello @abduraman,
Thanks for the bug report!
I already fixed a lot of issues like this one but missed this one.
2 Likes
It’s not as simple as that. Sometimes it’s in privacy custom token proof detail, sometimes somewhere else 
Fixed.
2 Likes
Sorry, forgot it. For v1 txs, the old one is correct.
Hey @inccry,
Here is another bug due to BSC introduction.
Currently, there are two PRV-pBNB pools: BEP2 (much more liquidity) and BEP20 (so low liquidity). Incscan shows BEP20 and because of that, liquidity chart of PRV-pBNB is also wrong.
1 Like
I guess BSC and not BSC tokens have the same symbol, pBNB?
Right. You can differentiate them via “OriginalSymbol” (empty vs BNB_BSC) parameter here: https://api.incognito.org/ptoken/list
BTC shielding and unshielding amounts are not correct since Portal V4 deployment. Amounts are 10x smaller than amounts shown on Incscan.
I’m waiting for a solution from Core Team to fix it.
5 Likes
False alarm: BTC amounts are ok except on transaction page for a burn tx, it should show a 10x smaller amount.
2 Likes
Fixed
2 Likes