Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transactions are not available #1015

Open
thegoldenmule opened this issue Jan 23, 2025 · 1 comment
Open

Transactions are not available #1015

thegoldenmule opened this issue Jan 23, 2025 · 1 comment

Comments

@thegoldenmule
Copy link

Describe the bug

On Porto, successful transactions are not showing up on accounts. We have tested with faucet, aptos_account::transfer_coins, and coins::transfer functions. None of them are available via the TS or Go APIs (via AccountTransactions functions), or the explorer.

To Reproduce

Steps to reproduce the behavior:

Option A

  1. Go to this account in the blockchain explorer: https://explorer.movementlabs.xyz/account/0xe9a90b610d2e0bc1c019d71ddbf80b3b00f4cc90dc54408b9050db947de5289f/transactions?network=testnet
  2. Note that there are 7 deposit events, but 0 transactions.

Option B (we have a deployed case)

  1. Create an account via a wallet provider.
  2. Fund with faucet or transfer.
  3. Go to explorer page for account.
  4. Note that there are no transactions for the account.

Code

Using the Go SDK:

var start uint64 = 0
var limit uint64 = 100
if transactions, err := client.AccountTransactions(address, &start, &limit); err == nil {
  util.Info(ctx, "@Count transactions retrieved.", len(transactions))
}

This logs out 0.

Expected behavior

All of these transactions should be available via the AccountTransactions call on the TS + Go APIs, as well as in the explorer. This includes faucet and transfers.

Screenshots

Here is a txn, function is 0x1::coin::transfer.

Image

Here is the recipient's account. Note that Balance is updated, as is deposit_events on the coinstore, but there are no transactions available.

Image


I tested the same code on Aptos' Devnet and I cannot reproduce. This is specific to Movement Porto (and maybe Bardock).

Here is an example of the same code creating a txn on Aptos devnet. The recipient account is updated and has the transactions available.

Image

@0xmovses
Copy link
Contributor

0xmovses commented Feb 6, 2025

Have you tested this on bardock? In any case we should repro and find the cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@thegoldenmule @0xmovses and others