You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.mdx
+5-8Lines changed: 5 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ The Go SDK library uses HTTP or gRPC APIs to communicate with the access nodes a
46
46
The library provides default factories for connecting to Flow AN APIs and you can easily switch between HTTP or gRPC if you use the provided client interface.
47
47
48
48
You can check more examples for creating clients in the examples:
@@ -452,7 +452,7 @@ Flow, like most blockchains, allows anybody to submit a transaction that mutates
452
452
Transaction data is composed and signed with help of the SDK. The signed payload of transaction then gets submitted to the access node API. If a transaction is invalid or the correct number of authorizing signatures are not provided, it gets rejected.
453
453
454
454
Executing a transaction requires couple of steps:
455
-
-[Building transaction](#build-transactions).
455
+
-[Building transaction](#build-the-transaction).
456
456
-[Signing transaction](#sign-transactions).
457
457
-[Sending transaction](#send-transactions).
458
458
@@ -586,15 +586,15 @@ func main() {
586
586
}
587
587
```
588
588
589
-
After you have successfully [built a transaction](#build-transactions) the next step in the process is to sign it.
589
+
After you have successfully [built a transaction](#build-the-transaction) the next step in the process is to sign it.
Flow introduces new concepts that allow for more flexibility when creating and signing transactions.
595
595
Before trying the examples below, we recommend that you read through the [transaction signature documentation](https://docs.onflow.org/concepts/accounts-and-keys/).
596
596
597
-
After you have successfully [built a transaction](#build-transactions) the next step in the process is to sign it. Flow transactions have envelope and payload signatures, and you should learn about each in the [signature documentation](https://docs.onflow.org/concepts/accounts-and-keys/#anatomy-of-a-transaction).
597
+
After you have successfully [built a transaction](#build-the-transaction) the next step in the process is to sign it. Flow transactions have envelope and payload signatures, and you should learn about each in the [signature documentation](https://docs.onflow.org/concepts/accounts-and-keys/#anatomy-of-a-transaction).
After a transaction has been [built](#build-transactions) and [signed](#sign-transactions), it can be sent to the Flow blockchain where it will be executed. If sending was successful you can then [retrieve the transaction result](#get-transactions).
879
+
After a transaction has been [built](#build-the-transaction) and [signed](#sign-transactions), it can be sent to the Flow blockchain where it will be executed. If sending was successful you can then [retrieve the transaction result](#get-transactions).
0 commit comments