Merge pull request #106 from smartcontractkit/ton-fix

JD: Use the correct field for TON configuration

Author: archseer

src/components/Form/ChainConfigurationForm.test.tsx

@@ -419,14 +419,14 @@ test('should able to create TON chain config', async () => {
   const address = container.querySelector('#select-accountAddr')
   expect(address).toBeInTheDocument()
   address && userEvent.click(address)
-  userEvent.click(getByRole('option', { name: 'ton_xxxx' }))
-  await screen.findByRole('button', { name: 'ton_xxxx' })
+  userEvent.click(getByRole('option', { name: '123' }))
+  await screen.findByRole('button', { name: '123' })
 
   await userEvent.click(getByRole('button', { name: /submit/i }))
 
   await waitFor(() => {
     expect(handleSubmit).toHaveBeenCalledWith({
-      accountAddr: 'ton_xxxx',
+      accountAddr: '123',
       accountAddrPubKey: '',
       adminAddr: '0x1234567',
       chainID: '5555',

src/components/Form/ChainConfigurationForm.tsx

@@ -266,7 +266,7 @@ export const ChainConfigurationForm = withStyles(styles)(
               break
             case ChainTypes.TON:
               chainAccountAddresses =
-                accountsNonEvm?.tonKeys.results.map((acc) => acc.id) ?? []
+                accountsNonEvm?.tonKeys.results.map((acc) => acc.addressBase64) ?? []
               break
             default:
               chainAccountAddresses = []