bittensor icon indicating copy to clipboard operation
bittensor copied to clipboard

Internet-scale Neural Networks

Results 190 bittensor issues
Sort by recently updated
recently updated
newest added

### Describe the bug I'm aware that this is not a bug but I'd like to discuss one scenario that I'm trying to implement in my environment. Turns out that...

bug

### Describe the bug It has been observed that throughout the Bittensor codebase, specifically within the subtensor module, several functions are defined with mutable default arguments. This is a common...

bug

### Describe the bug The `Balance` class within the Bittensor project has several comparison dunder methods (`__eq__`, `__ne__`, `__gt__`, `__lt__`) designed to handle comparisons with instances of `Balance` itself, or...

bug

### Describe the bug The `get_transfer_fee` method within the Subtensor class in the Bittensor project exhibits multiple significant issues, particularly in handling different types of token values (int, float, Balance)...

bug

This changes the flow of extrinsic submission. Currently, the flow suffers from a double-compose issue. Current flow if the submission has an exception (assume the initial submission is included in...

Introducing a new subprocess for the commit-reveal mechanism alongside necessary utility functions. Also added end-to-end tests to ensure proper functionality of the new subprocess feature.

Add the following fields to Metagraph class in `bittensor/rao` branch: - add LS (local stake) - GS (global stake) - SW (stake weights)

rao

- Until now ANSI was stripped from stdout if bittensor was not running within a TTY (like in PM2) by colorama when it was intialized - This caused colored output...

### Describe the bug When using ansi escape sequences with bittensor 6.9.4, the messages are correctly formatted, but not later (7.1.2 and 8.2.0 tested) versions. Even a simple `print()` before...

bug

### Bug #2361 ### Description of the Change Any instances where weights are being logged have been changed to `bt.logging.debug("weights", *weights)`. The bug occurs when we attempt to log with...