Skip to content

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Mar 1, 2023

Bumps debian from buster-20210311 to buster-20230227.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps debian from buster-20210311 to buster-20230227.

---
updated-dependencies:
- dependency-name: debian
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Mar 1, 2023

The following labels could not be found: docker, dependencies.

@cwq0202
Copy link

cwq0202 commented Nov 22, 2024

Hello, @msmouse

I noticed on GitHub that you are a key contributor to Diem. I am a blockchain developer and have a few questions regarding serialization that I’d like to ask:

1、What was the original purpose behind the design of Binary Canonical Serialization (BCS) in Diem?
2、Which canonical features were utilized in the serialization process?
3、I am planning to use Protobuf for serialization to support applications like digital signatures, information storage and etc. Diem did not adopt Google's Protobuf—was there a particular drawback or limitation with Protobuf that influenced this decision?

Sincerely wish your response,thanks!

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

Successfully merging this pull request may close these issues.

1 participant