Overview & Structure
The central access point to all services is made available through the AeternityService which can be obtained via the AeternityServiceFactory. Necessary parameters to f.e. identify the network to use or the endpoints to act against, are defined via the AeternityServiceConfiguration. Within this class, the following parameters can be set
Parameter | Description | Value / Default |
baseUrl | endpoint URL of the aeternity node | |
compilerBaseUrl | endpoint URL of the sophia compiler node | |
mdwBaseUrl | endpoint URL of the aeternal middleware | |
network | network to run against - must be considered together with chosen Endpoint URLs | |
nativeMode | for debug and test purposes - if true, the SDK creates the unsigned transaction from the given model, otherwise the node is called | true |
baseKeyPair | the account which is internally used to sign all transactions (if no other private key is passed in the post transaction method) | |
vertx | the vertx instance which is used within the SDK to call the node interfaces - will be instantiated automatically | |
targetVM | target VM version - depending on the selected VM, contract related transactions need to specify the respective abiVersion and vmVersion |
To actually construct the service configuration and get an instance of the AeternityService, the following steps are necessary. In this example we use a randomly created base key pair
KeyPairService keyPairService = new KeyPairServiceFactory().getService();
BaseKeyPair baseKeyPair = keyPairService.generateBaseKeyPair();
AeternityService aeternityService =
new AeternityServiceFactory()
.getService(
AeternityServiceConfiguration.configure()
.baseUrl(<baseURL>)
.compilerBaseUrl(<compilerBaseUrl>)
.aeternalBaseUrl(<aeternalBaseUrl>)
.network(Network.<network>)
.baseKeyPair(baseKeyPair)
.targetVM(VirtualMachine.FATE)
.compile());
All provided functions are classified into their purpose for better organization - those will be discussed in the subsequent chapters.
Last modified 2yr ago