BITCOIN BANK and BLOCK together

.devcontainer/Dockerfile

@@ -0,0 +1,11 @@
+# Use Rust base image
+FROM mcr.microsoft.com/devcontainers/rust:1
+
+# Install additional dependencies
+RUN apt-get update && apt-get install -y \
+    build-essential \
+    libdbus-1-dev \
+    gnome-keyring \
+    libxcb1-dev \
+    protobuf-compiler \
+    && apt-get clean

.devcontainer/devcontainer.json

@@ -0,0 +1,28 @@
+{
+    "name": "Rust Dev Container",
+    "build": {
+      "dockerfile": "Dockerfile"
+    },
+    "features": {
+      "ghcr.io/devcontainers/features/rust:1": {
+        "version": "stable"
+      }
+    },
+    "customizations": {
+      "vscode": {
+        "extensions": [
+          "rust-lang.rust-analyzer",
+          "vadimcn.vscode-lldb"
+        ]
+      },
+      "settings": {
+        "terminal.integrated.defaultProfile.linux": "/bin/bash"
+      }
+    },
+    "postCreateCommand": "cargo build",
+    "remoteUser": "vscode",
+    "mounts": [
+      "source=${localWorkspaceFolder}/crates,target=/workspace/crates,type=bind"
+    ]
+  }
+

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+
+Note: Please check the common issues on https://block.github.io/goose/docs/troubleshooting before filing a report
+
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Please provide following information:**
+ - **OS & Arch:** [e.g. Ubuntu 22.04 x86]
+ - **Interface:** [UI/CLI]
+ - **Version:** [e.g. v1.0.2]
+ - **Extensions enabled:** [e.g. Computer Controller, Figma]
+ - **Provider & Model:** [e.g. Google - gemini-1.5-pro]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Goose Discord discussion
+    url: https://discord.gg/block-opensource
+    about: Please ask and answer questions here.
+  - name: Report a security vulnerability
+    url: https://github.com/block/goose/security/policy
+    about: Please report security vulnerabilities here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: 'enhancement'
+assignees: ''
+
+---
+
+**Please explain the motivation behind the feature request.**
+Does this feature solve a particular problem you have been experiencing? What opportunities or use cases would be unlocked with this feature?
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+- [x] I have verified this does not duplicate an existing feature request

.github/ISSUE_TEMPLATE/submit-recipe.yml

@@ -0,0 +1,110 @@
+name: 🧑‍🍳 Submit a Recipe to the Goose Cookbook
+description: Share a reusable Goose recipe with the community!
+title: "[Recipe] <your recipe title here>"
+labels: ["recipe submission"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for contributing to the Goose Cookbook! 🍳  
+        Recipes are reusable sessions created in Goose Desktop or CLI and shared with the community to help others vibe code faster.
+
+        📌 **How to Submit**
+        - Create your recipe using Goose ("Make recipe from this session")
+        - Fill out the YAML below using the format provided
+        - Paste it into the field and submit the issue — we'll review and add it to the Cookbook!
+
+        🪄 **What Happens After?**
+        - If accepted, we'll publish your recipe to the [Goose Recipes Cookbook](https://block.github.io/goose/recipes)
+        - You'll receive OpenRouter **LLM API credits** as a thank you!
+        - Your GitHub handle will be displayed and linked on the recipe card
+        - If you provide an email below, we'll email you your credits when your recipe is approved and merged.
+        - If the YAML has any issues, Goose will comment with validation errors so you can fix and resubmit.
+
+        🧪 **Pro Tip:** You can test your recipe locally in your terminal with:  
+        `goose recipe validate your-recipe.yaml`
+
+  - type: textarea
+    id: recipe-yaml
+    attributes:
+      label: Paste Your Full Recipe YAML Below
+      description: Use the structure below and we’ll auto-fill your GitHub handle for `author.contact` after submission.
+      placeholder: |
+        version: "1.0.0"
+        id: clean-up-feature-flag
+        title: Clean Up Feature Flag
+        description: Automatically clean up all references of a fully rolled out feature flag from a codebase and make the new behavior the default.
+        instructions: |
+          Your job is to systematically remove a fully rolled out feature flag and ensure the new behavior is now the default. Use code search tools like ripgrep to identify all references to the flag, clean up definition files, usage sites, tests, and configuration files. Then create a commit and push changes with clear commit messages documenting the flag removal.
+        prompt: |
+          Task: Remove a feature flag that has been fully rolled out, where the feature flag's functionality should become the default behavior.
+
+          Context:
+            Feature flag key: {{ feature_flag_key }}
+            Project: {{ repo_dir }}
+
+          Steps to follow:
+            1. Check out a *new* branch from main or master named using the feature flag key.
+            2. Find the feature flag constant/object that wraps the key.
+            3. Search for all references to the constant/object using ripgrep or equivalent tools.
+            4. Remove all conditional logic and make the new behavior default.
+            5. Remove unused imports, mocks, config, and tests.
+            6. Commit your changes and push the branch.
+            7. Open a GitHub PR.
+
+          Use commit messages like:
+            chore(flag-cleanup): remove <feature_flag_key> flag from codebase
+
+        parameters:
+          - key: feature_flag_key
+            input_type: string
+            requirement: required
+            description: Key of the feature flag
+
+          - key: repo_dir
+            input_type: string
+            requirement: optional
+            default: ./
+            description: Directory of the codebase
+
+        extensions:
+          - type: stdio
+            name: developer
+            cmd: uvx
+            args:
+              - developer-mcp@latest
+            timeout: 300
+            bundled: true
+            description: Access developer tools
+
+        activities:
+          - Remove feature flag definitions
+          - Clean up feature flag usage sites
+          - Update affected tests
+          - Remove flag configurations
+          - Document flag removal
+    validations:
+      required: true
+
+  - type: input
+    id: email
+    attributes:
+      label: Your Email (optional)
+      description: If your recipe is approved, we'll email your LLM API credits here.
+      placeholder: yourname@example.com
+    validations:
+      required: false
+
+  - type: markdown
+    attributes:
+      value: |
+        🛠 **Recipe Field Tips**
+        - `version` must be "1.0.0" for now
+        - `id` should be lowercase, hyphenated, and unique (e.g. `my-awesome-recipe`)
+        - `title` is the display name of your recipe
+        - `description` should clearly explain what the recipe does
+        - `instructions` are specific steps Goose should follow — supports template variables like `{{ variable_name }}`
+        - `prompt` is the first thing Goose sees when the recipe is launched
+        - `parameters` should include required or optional inputs — optional ones must have `default`
+        - `extensions` must follow the full format with `type`, `cmd`, `args`, `timeout`, etc.
+        - `activities` describe the main actions the recipe performs

.github/workflows/autoclose

@@ -0,0 +1,23 @@
+name: Close inactive issues
+on:
+  schedule:
+    - cron: "30 1 * * *"
+
+jobs:
+  close-issues:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+      - uses: actions/stale@v9
+        with:
+          days-before-issue-stale: 60
+          days-before-issue-close: 21
+          stale-issue-label: "stale"
+          stale-issue-message: "This issue is stale because it has been open for 30 days with no activity."
+          close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
+          days-before-pr-stale: -1
+          days-before-pr-close: -1
+          any-of-labels: "bug,Bug"
+          repo-token: ${{ secrets.GITHUB_TOKEN }}