Guillem Córdoba

Hey! Could we get a little status update on this issue? Has any of this been resolved?

[ ] re-export `holo_hash` with the "encoding" feature so we don't have to keep enabling it in our Cargo.toml if we want to use B64 hashes: ```toml [dependencies] derive_more =...

Yeah, I like these names so far. I agree with @pdaoust that `hc_` makes more sense, I would not overload `hdk` with utility libraries (e.g. `hc_utils` was its own thing...

Perfect. > Related but that's also an issue I have with your reusable module template- it presumes each project is a single zome Mmm interesting. With that, I'm not suggesting...

Yeah and these constraints may be all changed if the "accessors" primitive gets finally implemented. If that's there available for us, maybe all we need to do is attach new...

Oh I also was investigating things like [rust-reflection](https://github.com/8BitMate/reflect) for low code things and looked promising after some initial tests... We could use it as a first step towards an ABI...

Nope I haven't, they were early explorations... And I have little experience with Rust macros.

I have also seen this in my PRs :)

This one is also flakey I think: https://app.circleci.com/pipelines/github/holochain/holochain/7522/workflows/e9041fb7-012a-47e3-8e82-7a7f68203ac8/jobs/9160

And also, in a bridged `call`, it would be potentially very useful to know the hash of the "caller DNA", and I think this is possible as far as the...