low_level
library
Exceptions / Errors
AddressFormatException
Parent class for exceptions thrown during address encoding and decoding.
An exception of type AddressFormatException should never be thrown; throw
one of the child types instead.
AddressFormatExceptionBitConvertFail
Exception thrown by Bech32Cosmos when convertBits fails
AddressFormatExceptionChecksumFail
Exception thrown by Bech32Cosmos when trying to decode an address with a bad checksum
AddressFormatExceptionDataLength
Exception thrown by Bech32Cosmos when trying to decode an address with a data part of incorrect length
AddressFormatExceptionHrpLength
Exception thrown by Bech32Cosmos when trying to encode an address with a bad human-readable part
AddressFormatExceptionInputLength
Exception thrown by Bech32Cosmos when trying to decode an address of incorrect length
AddressFormatExceptionInvalidCharacter
Exception thrown by Bech32Cosmos when trying to decode an address containing an invalid character
AddressFormatExceptionNoHrp
Exception thrown by Bech32Cosmos when trying to decode an address with no human-readable part
CookbookAlreadyExistsException
Exception thrown by TX-emitting API calls when a cookbook already exists
on chain while we're trying to create it.
CookbookDoesNotExistException
Exception thrown by TX-emitting API calls when a cookbook does not exist on
the chain.
CookbookNotOwnedException
Exception thrown by TX-emitting API calls when a cookbook cannot be modified
or a recipe cannot be created by the active profile because the cookbook is
owned by a different one.
ItemDoesNotExistException
Exception thrown by TX-emitting API calls when an item to be used in
executing a recipe or creating a trade does not exist.
ItemNotOwnedException
Exception thrown by TX-emitting API calls when an item to be used in
executing a recipe or creating a trade is not owned by the active profile.
NodeInternalErrorException
Exception thrown by TX-emitting API calls when the Pylons node has an
internal error during processing of the emitted TX. If this occurs in
production environments, that's a problem.
NotAnAddressException
Exception thrown by API calls that accept an address as an argument when
the supplied argument is not a valid address.
NoWalletException
Exception thrown by API calls when the wallet doesn't exist.
PaymentNotValidException
Exception thrown by TX-emitting API calls when a provided payment ID does
not exist or is not correct for the purchase being made.
ProfileDoesNotExistException
Exception thrown by API calls when a profile does not exist on the chain.
ProfileStateException
Exception thrown by TX-emitting API calls when a profile is not in a valid
state for the execution of a recipe.
RecipeAlreadyExistsException
Exception thrown by TX-emitting API calls when a recipe already exists
on chain at the coordinates one is trying to be created at.
RecipeDoesNotExistException
Exception thrown by TX-emitting API calls when a recipe does not exist on
the chain.
RecipeNotOwnedException
Exception thrown by TX-emitting API calls when a recipe cannot be modified
by the active profile because it's owned by a different one.
RecipeStateException
Exception thrown by TX-emitting API calls when a recipe is not in a valid
state for the operation that the transaction attempted to perform.
RecipeValidationException
Exception thrown by TX-emitting API calls when a recipe fails the sanity
check performed before the transaction is generated.
ResponseException
Exception thrown when an outgoing message gets an illegal response.
This should not be seen in production environments.
UnhandledErrorException
Exception thrown by API calls when they get an error they aren't prepared
for. This should absolutely, 100 percent never be seen in production
environments.
WalletInitializationAlreadyDoneException
Exception thrown when the user tries to setup the wallet again
WalletInitializationNotDone
Exception thrown when the user tries to setup the wallet again
