Noir Contracts: Can TransparentNote of the non_native_token_contract conform to the NoteInterface?

[iAmMichaelConnor]

Ideally, we should be able to design every custom note to adhere to the NoteInterface:

use crate::note::note_header::NoteHeader;

struct NoteInterface<Note, N> {
    deserialise: fn ([Field; N]) -> Note,

    serialise: fn (Note) -> [Field; N],

    compute_note_hash: fn (Note) -> Field,

    compute_nullifier: fn (Note) -> Field,

    dummy: fn () -> Note,

    get_header: fn (Note) -> NoteHeader,

    set_header: fn (&mut Note, NoteHeader) -> (),
}

The motivation for this, is that an ordinary (not advanced) user can write notes without having to mention the Aztec context or the abi. This is because the Set, Singleton and ImmutableSingleton types take care of pushing-to and pulling-from the context, abis, and trees, by wrapping custom notes.

Currently, the TransparentNote deviates from this pattern. I don't fully understand the example, but would like to understand if the note could be made to conform to the pattern, or if there's something fundamental that's been overlooked in designing the NoteInterface.

Tagging @Maddiaa0 who I think designed this contract and note :)

[dbanks12]

It can, and I have started working on this here #1194

[dbanks12]

Closed as this is being done in #1194