Publish Prep

.gitignore

@@ -1 +1,17 @@
-.DS_Store
+# https://dart.dev/guides/libraries/private-files
+# Created by `dart pub`
+.dart_tool/
+
+# Avoid committing pubspec.lock for library packages; see
+# https://dart.dev/guides/libraries/private-files#pubspeclock.
+pubspec.lock
+
+# Flutter/Dart/Pub related
+**/doc/api/
+**/ios/Flutter/.last_build_id
+.dart_tool/
+.flutter-plugins
+.flutter-plugins-dependencies
+.pub-cache/
+.pub/
+/build/

.pubignore

@@ -0,0 +1,3 @@
+bin
+web5-spec
+Justfile

CHANGELOG.md

@@ -1,3 +1,3 @@
-## 1.0.0
+## 0.1.0
 
 - Initial version.

CODEOWNERS

@@ -1 +1,24 @@
-*            @mistermoe @ethan-tbd @kirahsapong @wesbillman @diehuxx
+# This CODEOWNERS file denotes the project leads
+# and encodes their responsibilities for code review.
+
+# Instructions: At a minimum, replace the '@GITHUB_USER_NAME_GOES_HERE'
+# here with at least one project lead.
+
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+# The format is described: https://github.blog/2017-07-06-introducing-code-owners/
+
+# These owners will be the default owners for everything in the repo.
+* @ethan-tbd @mistermoe @wesbillman
+
+
+# -----------------------------------------------
+# BELOW THIS LINE ARE TEMPLATES, UNUSED
+# -----------------------------------------------
+# Order is important. The last matching pattern has the most precedence.
+# So if a pull request only touches javascript files, only these owners
+# will be requested to review.
+# *.js    @octocat @github/js
+
+# You can also use email addresses if you prefer.
+# docs/*  [email protected]

CODE_OF_CONDUCT.md

@@ -0,0 +1,136 @@
+
+# TBD Code of Conduct
+
+TBD builds infrastructure for the next wave of innovation in financial services — which we believe will be decentralized, permissionless, and non-custodial. This means opening the global economy to everyone. We extend the same principles of inclusion to our developer ecosystem. We are excited to build with you. So we will ensure our community is truly open, transparent and inclusive. Because of the global nature of our project, diversity and inclusivity is paramount to our success. We not only welcome diverse perspectives, we **need** them!
+
+The code of conduct below reflects the expectations for ourselves and for our community.
+
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, physical appearance, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful and welcoming of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+The TBD Open Source Governance Committee (GC) is responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+The GC has the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event, or any space where the project is listed as part of your profile.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the TBD Open Source Governance Committee (GC) at
+`[email protected]`.
+All complaints will be reviewed and investigated promptly and fairly.
+
+The GC is obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+The GC will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from the GC, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media and forums. 
+
+Although this list cannot be exhaustive, we explicitly honor diversity in age, culture, ethnicity, gender identity or expression, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected characteristics above, including participants with disabilities.
+
+Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

Justfile

@@ -1,29 +1,23 @@
+_help:
+  @just -l
+
 get:
   #!/bin/bash
+  set -euo pipefail
+
   echo "Getting dependencies for packages"
-  for dir in packages/*; do \
-    if [ -d $dir ]; then \
-      echo "Getting dependencies in $dir"; \
-      (cd $dir && flutter pub get || dart pub get); \
-    fi \
-  done
+  dart pub get
 
-test: test-vectors
+test:
   #!/bin/bash
-  for dir in packages/*; do \
-    if [ -d $dir ]; then \
-      echo "Running tests in $dir"; \
-      (cd $dir && flutter test || dart test); \
-    fi \
-  done
+  set -euo pipefail
+
+  git submodule init
+  git submodule update
+  dart test
 
 analyze:
   #!/bin/bash
-  for dir in packages/*; do \
-    if [ -d $dir ]; then \
-      (cd $dir && flutter analyze || dart analyze); \
-    fi \
-  done 
+  set -euo pipefail
 
-test-vectors:
-  @git submodule update --init --recursive
+  dart analyze

README.md

@@ -1,39 +1,7 @@
-<!-- 
-This README describes the package. If you publish this package to pub.dev,
-this README's contents appear on the landing page for your package.
+Dart SDK for [Web5](https://github.com/TBD54566975/web5-spec?tab=readme-ov-file#web5-sdk-features)
 
-For information about how to write a good package README, see the guide for
-[writing package pages](https://dart.dev/guides/libraries/writing-package-pages). 
 
-For general information about developing packages, see the Dart guide for
-[creating packages](https://dart.dev/guides/libraries/create-library-packages)
-and the Flutter guide for
-[developing packages and plugins](https://flutter.dev/developing-packages). 
--->
+![GitHub License](https://img.shields.io/github/license/tbd54566975/web5-dart) ![GitHub Actions Workflow Status](https://img.shields.io/github/actions/workflow/status/tbd54566975/web5-dart/ci.yaml) ![Pub Version](https://img.shields.io/pub/v/typeid?link=https%3A%2F%2Fpub.dev%2Fpackages%2Fweb5) ![Pub Publisher](https://img.shields.io/pub/publisher/web5) ![Pub Points](https://img.shields.io/pub/points/web5)
 
-TODO: Put a short description of the package here that helps potential users
-know whether this package might be useful for them.
-
-## Features
-
-TODO: List what your package can do. Maybe include images, gifs, or videos.
-
-## Getting started
-
-TODO: List prerequisites and provide or point to information on how to
-start using the package.
-
-## Usage
-
-TODO: Include short and useful examples for package users. Add longer examples
-to `/example` folder. 
-
-```dart
-const like = 'sample';
-```
-
-## Additional information
-
-TODO: Tell users more about the package: where to find more information, how to 
-contribute to the package, how to file issues, what response they can expect 
-from the package authors, and more.
+> [!WARNING]
+> 🚧 WIP 👷

packages/web5/test/crypto/secp256k1_test.dart → test/crypto/secp256k1_test.dart

@@ -7,7 +7,7 @@ import 'package:web5/src/crypto.dart';
 import 'package:test/test.dart';
 
 final thisDir = Directory.current.path;
-final vectorDir = '$thisDir/../../web5-spec/test-vectors/crypto_es256k';
+final vectorDir = '$thisDir/web5-spec/test-vectors/crypto_es256k';
 
 class Input {
   String data;

packages/web5/test/helpers/test_vector_helpers.dart → test/helpers/test_vector_helpers.dart

@@ -2,7 +2,7 @@ import 'dart:convert';
 import 'dart:io';
 
 final thisDir = Directory.current.path;
-final vectorDir = '$thisDir/../../web5-spec/test-vectors/';
+final vectorDir = '$thisDir/web5-spec/test-vectors/';
 
 Map<String, dynamic> getJsonVectors(String vectorSubPath) {
   final vectorPath = '$vectorDir$vectorSubPath';