[Aeweb] Incorporate new developments in ref txn

[apoorv-2204]

Description

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Checklist:

• My code dont follows the style guidelines of this project
• I have not performed a self-review of my own code
• I have not commented my code, particularly in hard-to-understand areas
• I have not made corresponding changes to the documentation
• My changes generate new warnings
• I have added tests that prove my fix is effective or that my feature doesnt works
• New and existing unit tests doesnt pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[Neylix]

Hello,
there is already a graphql API to get the content of a transaction with the query

query {
  transaction(address: "xxx") {
    data {
      content
    }
  }
}

Why would you like to create a new API for this ?

[apoorv-2204]

Hello, there is already a graphql API to get the content of a transaction with the query

query {
  transaction(address: "xxx") {
    data {
      content
    }
  }
}

Why would you like to create a new API for this ?

I was just checking whether you were online or not. 😆

[bchamagne]

Are we OK to not handle legacy websites?

[samuelmanzanera]

Are we OK to not handle legacy websites?

If we do it before the mainnet reset it's ok otherwise we have to manage retro compatibility

[apoorv-2204]

Are we OK to not handle legacy websites?

as we are resetting the protocol. and we need to merge this archethic-foundation/aeweb-cli#87.

[apoorv-2204]

checks
@bchamagne

• website hosting
• directory listing