Skip to content

Releases: kinode-dao/kinode

Beta 0.7.2

08 May 21:37
4637b1f
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

Contains the usual bugfixes, and a large improvement to the node user interface.

The homepage and app store frontends have been redone, adding the ability to create and use "widgets". We've also added a "system settings" page, still rough around the edges, but useful for debugging in beta.

To showcase widgets, we've added one for the app store and one to display recent news from kinode.org.

Simulation mode (fake nodes) have also been overhauled, including a new networking strategy and the ability to work against a fake local EVM chain. This is quite useful in conjunction with recent updates to kit.

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

For developers, make sure to follow the instructions for 0.7.0 if upgrading from 0.6.x or earlier: https://github.com/kinode-dao/kinode/releases/tag/v0.7.0

What's Changed

Full Changelog: v0.7.1...v0.7.2

v0.7.1

01 May 17:23
5504f2a
Compare
Choose a tag to compare

Contains bugfixes and frontend improvements.

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

For developers, make sure to follow the instructions for 0.7.0 if upgrading from 0.6.x or earlier: https://github.com/kinode-dao/kinode/releases/tag/v0.7.0

What's Changed

Full Changelog: v0.7.0...v0.7.1

Beta 0.7.0

18 Apr 17:10
b699f3f
Compare
Choose a tag to compare

7th major alpha/beta release.

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

For this update, process devs with existing processes are recommended to:

  1. Bump process_lib import:
    process_lib = { git = "https://github.com/kinode-dao/process_lib.git", tag = "v0.6.1" }
    
  2. Bump wit-bindgen:
    wit-bindgen = "0.24.0"
    
  3. Use the newest kit:
    kit update
    
  4. Change the wit_bindgen::generate!() call to remove the exports field:
    wit_bindgen::generate!({
         path: "wit",
         world: "process",
    });
    
  5. If not using call_init!(), add export!() macro call:
    export!(Component);
    

What's Changed

New Contributors

Full Changelog: v0.6.2...v0.7.0

Beta 0.6.2

02 Apr 19:02
1d8c6d5
Compare
Choose a tag to compare

Small fixes related to hostable nodes and registration frontend.

Boot instructions have not changed, but can now use the --ws-routing port to enforce a given port for the websockets-based networking protocol.

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

For most purposes, you should be booting a testnet node on ETH Sepolia:

./kinode home/mynodename --testnet

Testnet nodes must use the --testnet flag on boot.

What's Changed

New Contributors

Full Changelog: v0.6.1...v0.6.2

Beta 0.6.1

18 Mar 14:38
1a3de8d
Compare
Choose a tag to compare
Beta 0.6.1 Pre-release
Pre-release

Bugfix release. Fixes some aspects of process exit behavior (more to be done here) and fixes dev workflow around booting fake nodes (--simulation-mode flag).

Boot instructions have not changed from the previous release:

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

For most purposes, you should be booting a testnet node on ETH Sepolia:

./kinode home/mynodename --testnet

Testnet nodes must use the --testnet flag on boot.

What's Changed

  • fix: kernel: do not reboot persisted processes if their OnExit behavior is None by @dr-frmr in #278
  • hotfix: use kit --features flag to pass simulation-mode and fix kit s by @nick1udwig in #279
  • hotfix: fix a bad merge by @nick1udwig in #280

Full Changelog: v0.6.0...v0.6.1

Beta 0.6.0

11 Mar 15:59
fccff76
Compare
Choose a tag to compare
Beta 0.6.0 Pre-release
Pre-release

This release of Kinode OS contains breaking changes to several APIs: eth:distro:sys, app_store:sys, terminal:sys, the capabilities system, and the package metadata format. The version of WASI used has been updated, meaning that apps must also update their WASI dependency. Apps should also upgrade to the new kinode_process_lib version 0.6.0. Lastly, the password/login system has changed to provide more security in a hosted environment. Nodes that were booted with 0.5.x versions must reset their passwords. Note that the runtime has not undergone any security audits and must be used at your own risk.

eth:distro:sys

The RPC Provider runtime module has been rewritten to support multiple chain IDs and multiple data sources, which can either be RPC URLs or other nodes. The API has changed to include chain ID in requests. Full API docs here: https://book.kinode.org/apis/eth_provider.html

app_store:sys

The App Store has undergone breaking changes in order to unify onchain app metadata and package metadata. The format of the metadata.json file has changed such that it can be the metadata for the app's ERC-721 onchain. See here for the new format: https://book.kinode.org/my_first_app/chapter_1.html#metadatajson

terminal:sys

Scripts have been adjusted slightly using the new capabilities system. Piping has been removed because it was unintuitive/buggy. It may be reintroduced in the future.

Capabilities

The kernel now has functionality to drop capabilities from a process, which can be accessed by a new function in kinode.wit: drop-capabilities. A process can only drop its own capabilities, but root access to the kernel includes the ability to drop capabilities from any process.

Boot instructions have changed:

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:
./kinode home/mynodename

For most purposes, you should be booting a testnet node on ETH Sepolia:

./kinode home/mynodename --testnet
Testnet nodes must use the --testnet flag on boot.

What's Changed

Full Changelog: v0.5.3-alpha...v0.6.0

Alpha 0.5.3

07 Feb 17:24
9b0ca2e
Compare
Choose a tag to compare
Alpha 0.5.3 Pre-release
Pre-release

Add "App Store", a new distro process that hooks into Kinode's onchain app store. Runs on ETH Sepolia testnet only. App Store will be empty on an Optimism node.

Runtime extensions are now supported. See docs for info.

Bug fixes and general improvements. scripts.json uses snake_case dictionary keys as was originally intended. Nodes will no longer boot if they are run with/without the testnet flag if they were originally booted on/off the testnet.

Known issue: OnExit::Requests behavior is incorrect. Will be fixed in next release!

Boot instructions remain the same:

To run the binary, you must indicate where the home folder for the node will be and use an --rpc-url flag. You may also optionally specify your HTTP port. Here's an example:

./kinode home/mynodename --rpc wss://opt-mainnet.g.alchemy.com/v2/<RPC_API_KEY> --port 8080
Note that the RPC provider is set to Optimism Mainnet. This is where the identity contract is deployed. You may also boot a testnet node on ETH Sepolia:

./kinode home/mynodename --rpc wss://eth-sepolia.g.alchemy.com/v2/<RPC_API_KEY> --port 8081 --testnet
Testnet nodes must use the --testnet flag on boot.

What's Changed

Full Changelog: v0.5.2-alpha...v0.5.3-alpha

Alpha 0.5.2

30 Jan 05:34
5e4bfc3
Compare
Choose a tag to compare
Alpha 0.5.2 Pre-release
Pre-release

Bug fixes and general improvements.

"Breaking changes", not to process development, but to terminal usage. Terminal no longer uses / commands, but rather uses scripting. Scripting is also now available to all processes: see terminal:sys and app_store:sys in this repo for examples of doing so. Scripts can be called by using their name in the terminal and then writing our their arguments. See README for examples.

Boot instructions remain the same:

To run the binary, you must indicate where the home folder for the node will be and use an --rpc-url flag. You may also optionally specify your HTTP port. Here's an example:

./kinode home/mynodename --rpc wss://opt-mainnet.g.alchemy.com/v2/<RPC_API_KEY> --port 8080

Note that the RPC provider is set to Optimism Mainnet. This is where the identity contract is deployed. You may also boot a testnet node on ETH Sepolia:

./kinode home/mynodename --rpc wss://eth-sepolia.g.alchemy.com/v2/<RPC_API_KEY> --port 8081 --testnet

Testnet nodes must use the --testnet flag on boot.

What's Changed

Full Changelog: v0.5.1-alpha...v0.5.2-alpha

Alpha 0.5.1

22 Jan 00:49
33f9af8
Compare
Choose a tag to compare
Alpha 0.5.1 Pre-release
Pre-release

To run the binary, you must indicate where the home folder for the node will be and use an --rpc-url flag. You may also optionally specify your HTTP port. Here's an example:

./kinode home/mynodename --rpc wss://opt-mainnet.g.alchemy.com/v2/<RPC_API_KEY> --port 8080

Note that the RPC provider is set to Optimism Mainnet. This is where the identity contract is deployed. You may also boot a testnet node on ETH Sepolia:

./kinode home/mynodename --rpc wss://eth-sepolia.g.alchemy.com/v2/<RPC_API_KEY> --port 8081 --testnet

Testnet nodes must use the --testnet flag on boot.

What's Changed

Full Changelog: v0.5.0-alpha...v0.5.1-alpha

Alpha 0.5.0

17 Jan 22:06
173c89d
Compare
Choose a tag to compare
Alpha 0.5.0 Pre-release
Pre-release

First release under the new name: Kinode

To run the binary, you must indicate where the home folder for the node will be and use an --rpc-url flag. You may also optionally specify your HTTP port. Here's an example:

./kinode home/mynodename --rpc wss://opt-mainnet.g.alchemy.com/v2/<RPC_API_KEY> --port 8080

Note that the RPC provider is set to Optimism Mainnet. This is where the identity contract is deployed. You may also boot a testnet node on ETH Sepolia:

./kinode home/mynodename --rpc wss://eth-sepolia.g.alchemy.com/v2/<RPC_API_KEY> --port 8081 --testnet

Testnet nodes must use the --testnet flag on boot.

What's Changed

Full Changelog: v0.4.0-alpha...v0.5.0-alpha