babylon-node icon indicating copy to clipboard operation
babylon-node copied to clipboard

The Radix node, updated for Babylon. Embeds the Radix engine which lives at https://github.com/radixdlt/radixdlt-scrypto.

Results 12 babylon-node issues
Sort by recently updated
recently updated
newest added

Follow-up changes for NODE-427 (event renaming). Cleaned up most uses of CoreEvent and removed some unused code.

Small change, which reduces the frequency of the RATE_LIMIT message and shifts it to INFO level. Remaining messages logged at DEBUG level.

Exports Radix Engine structures. Done so that clients can more easily integrate with both Node/RadixEngine structures without needing to deal with the dependency mess.

## Summary When working on "staged instantiation" (needed for https://radixdlt.atlassian.net/browse/NODE-648) I noticed a refactoring opportunity: the "current protocol version" wasn't really updated by `TransactionTracker`, and it was a bit confusing...

## Summary Addresses https://radixdlt.atlassian.net/browse/NODE-637 pretty exactly, as the title says. ## Testing Existing regression must pass; only the handling of defaults has changed.

All set windows environment variables can be retrieved with the power shell command: gci env:* | sort-object name There might also be other techniques how applications could retrieve these settings,...

Try/test 1: Spaces in folder name of corerust.dll: ``` G:\Tools\Radix\version 1.1.3.1\Node\core-v1.1.3.1\bin>core 2024-05-01T14:47:02,909 [INFO/MemoryLeakDetector/main] - Starting memory leak detector... 2024-05-01T14:47:02,911 [OFF/RadixNodeApplication/main] - Radix distributed ledger 'v1.1.3.1' from branch '' commit 'dc9f98162b383a54b557be4867af4c09394837fe'...

https://docs.radixdlt.com/v1/docs/node-setup-systemd This tutorial is closest to how Windows Radix Node would be set up, but some of it is a little peculiar and could lead to problems. Would be nice...

Adds (all optional): - `projected_fulfillment_at_start_of_epoch` and `projected_fulfillment_timestamp` for each threshold of a pending protocol update - `projected_enactment_at_start_of_epoch` and `projected_enactment_timestamp` to a pending protocol update, which are the values of the...