Feature Request: Transactions by address.

[hkey0]

Hello, I have a few ideas about improving namadexer.

• List of transactions of the specified transparent address.
• List of all validators (with total stake)

It would be great if it had these features.

[rllola]

Hey @hkey0

Looks like good ideas. We will work on this ASAP.

[rllola]

List of transactions of the specified transparent address.

Unfortunately today we don't have all the decrypted info in a table so researching through addresses will return incomplete answer. However there is a solution proposed by my colleague to store the arbitrary data as JSON and postgres could handle searching in the JSON string. However it could impact negatively the performances.

[hkey0]

List of transactions of the specified transparent address.

Unfortunately today we don't have all the decrypted info in a table so researching through addresses will return incomplete answer. However there is a solution proposed by my colleague to store the arbitrary data as JSON and postgres could handle searching in the JSON string. However it could impact negatively the performances.

Can't we see all transactions of transparent addresses? Why can't we do that?

[rllola]

Can't we see all transactions of transparent addresses? Why can't we do that?

Because the addresses are in the blob of data and we don't know how to look them up in sql. Unless like mentioned we store it in JSON.

We are currently looking at this approach.

[hkey0]

Can't we see all transactions of transparent addresses? Why can't we do that?

Because the addresses are in the blob of data and we don't know how to look them up in sql. Unless like mentioned we store it in JSON.

We are currently looking at this approach.

Is it possible to use the tx search in cometbft?
Querying Transactions Events: https://docs.cometbft.com/v0.37/app-dev/indexing-transactions

[opsecx]

Can't we see all transactions of transparent addresses? Why can't we do that?

Because the addresses are in the blob of data and we don't know how to look them up in sql. Unless like mentioned we store it in JSON.

We are currently looking at this approach.

aren't all the transactions already in a separate table? I can see all of them in the indexer currently? (pretor)

[rllola]

I have started to work on this.

@opsecx In the current main branch we don't have the tx_transfer table anymore instead all the data are stored as JSON object in the transactions table. Also tx_transfer transaction might not represent all the transactions associated with an address. So now we can collect from all other kind of transactions.

I will share here the draft PR when it is ready.

[opsecx]

So all applications built to old format will fail if pulling the revised source tree? that's a lot of extra work on this end

[opsecx]

I have to say that breaking changes like these are extremely inconvenient

[rllola]

So all applications built to old format will fail if pulling the revised source tree? that's a lot of extra work on this end

No there is no breaking changes on the endpoints. You should be all good.

[opsecx]

So all applications built to old format will fail if pulling the revised source tree? that's a lot of extra work on this end

No there is no breaking changes on the endpoints. You should be all good.

I'm drawing directly off the db, so I'm assuming the answer to the question is yes

[rllola]

Done with #161