aepp-sdk-java
Search…
Overview & Structure
SDK Service Entrypoint
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
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
1
KeyPairService keyPairService = new KeyPairServiceFactory().getService();
2
BaseKeyPair baseKeyPair = keyPairService.generateBaseKeyPair();
3
AeternityService aeternityService =
4
new AeternityServiceFactory()
5
.getService(
6
AeternityServiceConfiguration.configure()
7
.baseUrl(<baseURL>)
8
.compilerBaseUrl(<compilerBaseUrl>)
9
.aeternalBaseUrl(<aeternalBaseUrl>)
10
.network(Network.<network>)
11
.baseKeyPair(baseKeyPair)
12
.targetVM(VirtualMachine.FATE)
13
.compile());
Copied!
Aeternity Service Capabilities
All provided functions are classified into their purpose for better organization - those will be discussed in the subsequent chapters.
accounts
aeternal
compiler
info
names
oracles
transactions
Last modified 8mo ago