chore: update config

[skywardboundd]

Closes #148

Summary by CodeRabbit

• Tests

  • Adjusted an opcode test expectation to reflect updated behavior.

• Chores

  • Updated default/slim configuration payloads and associated sequence.

• Documentation

  • Bumped package version to 0.42.0 and added changelog entry noting a ~6× reduction in transaction fees due to the updated configs.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a618727e-97fb-4eae-b904-5befbe0efef8

📥 Commits

Reviewing files that changed from the base of the PR and between 731b453 and 31eaa0a.

📒 Files selected for processing (4)

• CHANGELOG.md
• package.json
• src/config/defaultConfig.ts
• src/config/slimConfig.ts

---

📝 Walkthrough

Walkthrough

Updated the slim config constant and payload, bumped package version and changelog entry, and adjusted one test expectation from 40000n to 6667n.

Changes

Release / Config / Test Update

Layer / File(s)	Summary
Config Data src/config/slimConfig.ts	slimConfigSeqno updated to 64669801 and the slimConfig template-string payload replaced with a new configuration payload.
Behavioral/Test src/blockchain/Blockchain.spec.ts	Test assertion in should support TVM v6 opcodes changed: expected readBigNumber() result from 40000n → 6667n.
Release Wiring package.json	Package version bumped from 0.41.0 → 0.42.0.
Documentation / Changelog CHANGELOG.md	Added [0.42.0] entry (2026-05-04) noting configs updated to latest release-time config and ~6× fee reduction.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰
Soft configs hop to newer light,
Numbers trimmed and tests made right.
A tiny bump, a changelog line,
The network hums — all set, sublime. 🥕

🚥 Pre-merge checks | ✅ 1 | ❌ 4

❌ Failed checks (1 warning, 3 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal and incomplete. It closes issue #148 but omits all required template sections including CHANGELOG updates, README documentation, and test verification.	Complete the pull request description by filling out all required checklist items and documenting what was changed and why.
Title check	❓ Inconclusive	The title 'chore: update config' is vague and generic, lacking specific details about what config is being updated or why.	Consider making the title more specific, such as 'chore: update slimConfig version and TVM test assertion' to better describe the changes.
Linked Issues check	❓ Inconclusive	The linked issue #148 provides no coding requirements or objectives to validate against, making compliance assessment impossible.	Ensure the linked issue #148 contains specific requirements or objectives that can be used to validate the code changes.
Out of Scope Changes check	❓ Inconclusive	Changes include a test assertion update and config updates, but without issue #148 details, scope validation cannot be definitively determined.	Clarify the scope and objectives in issue #148 to determine if all changes are within the intended scope.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 148-update-config

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

src/config/slimConfig.ts (1)

1-2: ⚡ Quick win

Add provenance metadata for this config snapshot.

Please add a short comment near Line [1] / Line [2] documenting source network, fetch date, and source reference (endpoint/tool). Updating an opaque blob without provenance makes future validation and rollback harder.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/slimConfig.ts` around lines 1 - 2, Add provenance metadata as a
brief comment above the exported constants slimConfigSeqno and slimConfig:
include the source network (e.g., "mainnet" or "testnet"), the fetch date/time
(ISO 8601), and the original source reference (API endpoint, tool, or repo
commit hash) used to obtain the blob; place this comment adjacent to the exports
for slimConfigSeqno and slimConfig so future reviewers can trace the snapshot
without changing the exported variable names or values.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/config/slimConfig.ts`:
- Around line 1-2: Add provenance metadata as a brief comment above the exported
constants slimConfigSeqno and slimConfig: include the source network (e.g.,
"mainnet" or "testnet"), the fetch date/time (ISO 8601), and the original source
reference (API endpoint, tool, or repo commit hash) used to obtain the blob;
place this comment adjacent to the exports for slimConfigSeqno and slimConfig so
future reviewers can trace the snapshot without changing the exported variable
names or values.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: dd638b75-5610-46cb-996d-71f568ca8db9

📥 Commits

Reviewing files that changed from the base of the PR and between 2c404c1 and 731b453.

⛔ Files ignored due to path filters (1)

• src/metric/__snapshots__/collectMetric.spec.ts.snap is excluded by !**/*.snap

📒 Files selected for processing (3)

• src/blockchain/Blockchain.spec.ts
• src/config/defaultConfig.ts
• src/config/slimConfig.ts