This SDK helps developers get started with the on-chain tools provided by Metaplex. It focuses its API on common use-cases to provide a smooth developer experience.
Please check the Sample App.
From Xcode 11, you can use Swift Package Manager to add Solana.swift to your project.
- File > Swift Packages > Add Package Dependency
- Add
https://github.com/metaplex-foundation/metaplex-ios - Select "brach" with "master"
- Select Metaplex
If you encounter any problem or have a question on adding the package to an Xcode project, I suggest reading the Adding Package Dependencies to Your App guide article from Apple.
- iOS 11.0+ / macOS 10.13+ / tvOS 11.0+ / watchOS 3.0+
- Swift 5.3+
The entry point to the Swift SDK is a Metaplex instance that will give you access to its API.
Set the SolanaConnectionDriver and setup your enviroment. Provide a StorageDriver and IdentityDriver. You can also use the concrete implementations URLSharedStorageDriver for URLShared and GuestIdentityDriver for a guest Indentity Driver.
You can customise who the SDK should interact on behalf of and which storage provider to use when uploading assets. We might provide a default and simple implementation in the future.
let solanaDriver = SolanaConnectionDriver(endpoint: RPCEndpoint.mainnetBetaSolana)
let identityDriver = GuestIdentityDriver(solanaRPC: solana.solanaRPC)
let storageDriver = URLSharedStorageDriver(urlSession: URLSession.shared)
let metaplex Metaplex(connection: solana, identityDriver: identityDriver, storageDriver: storageDriver)Once properly configured, that Metaplex instance can be used to access modules providing different sets of features. Currently, there is only one NFT module that can be accessed via the nfts() method. From that module, you will be able to find, create and update NFTs with more features to come.
Lets dive in nfts module.
The NFT module can be accessed via Metaplex.nfts() and provide the following methods. Currently we only support readding methods. Writing and creating NFTs will be suported on the future.
findNftByMint(mint, callback)findNftByMintList(mints, callback)findNftsByOwner(owner, callback)findNftsByCreator(creator, position = 1, callback)findNftsByCandyMachine(candyMachine, version = 2, callback)
All the methods return a callback. Its also posible to wrap them inside either RX, and async Result or Combine. We only provide this interface since is the most compatible without forcing any specific framework.
The findNftByMint method accepts a mint public key and returns NFT object..
let ownerPublicKey = PublicKey(string: "HG2gLyDxmYGUfNWnvf81bJQj38twnF2aQivpkxficJbn")!
let nft = metaplex.nft.findNftByMint(publicKey: mintPublicKey) { result in
switch result {
case .success(let nft):
...
case .failure:
...
}
}The returned Nft object. This nft will be not contain json data. It will only contain on-chain data. If you need access to the JSON offchain Metadata you can call. This call requires the metaplex object.
nft.metadata(metaplex: self.metaplex) { result in
switch result {
case .success(let metadata):
...
case .failure:
...
}
}Similarly, the MasterEditionAccount account of the NFT will also be already loaded and, if it exists on that NFT, you can use it like so.
let masterEdition = nft.masterEditionAccountDepending on the MasterEditionAccount version it can return v1 or v2 enums.
You can read more about the NFT model below.
The findNftByMintList method accepts an array of mint addresses and returns an array of Nfts. However, nil values will be returned for each provided mint address that is not associated with an NFT.
let nft = metaplex.nft.findNftByMintList(mintKeys: [mintPublicKey, mintPublicKey]) { result in
switch result {
case .success(let nfts):
// You can use nftList.compactMap{ $0 } to remove nils
...
case .failure:
...
}
}NFTs retrieved via findNftByMintList will not have their JSON metadata loaded because this would require one request per NFT and could be inefficient if you provide a long list of mint addresses. Additionally, you might want to fetch these on-demand, as the NFTs are being displayed on your web app for instance.
Thus, if you want to load the JSON metadata of an NFT, you may do this like so.
nft.metadata(metaplex: self.metaplex) { result in
switch result {
case .success(let metadata):
...
case .failure:
...
}
}We'll talk more about these tasks when documenting the NFT model.
The findNftsByOwner method accepts a public key and returns all Nfts owned by that owner public key.
metaplex.nft.findNftsByOwner(publicKey: ownerPublicKey) { [weak self] result in
switch result {
case .success(let nftList):
...
case .failure:
...
}
}Similarly to findNftByMintList, the returned Nfts will not have their JSON metadata. This method is used on the Sample App.
All of the methods above either return or interact with an Nft object. The Nft object is a read-only data representation of your NFT that contains all the information you need at the top level.
You can see its full data representation by checking the code but here is an overview of the properties that are available on the Nft object.
// Always loaded.
public let metadataAccount: MetadataAccount
public let updateAuthority: PublicKey
public let mint: PublicKey
public let name: String
public let symbol: String
public let uri: String
public let sellerFeeBasisPoints: UInt16
public let creators: [MetaplexCreator]
public let primarySaleHappened: Bool
public let isMutable: Bool
public let editionNonce: UInt8?
// Sometimes loaded.
public let masterEditionAccount: MasterEditionAccount?As you can see, some of the properties are loaded on demand. This is because they are not always needed and/or can be expensive to load.
In order to load these properties, you may run the metadata properties of the Nft object.
nft.metadata(metaplex: self.metaplex) { result in
switch result {
case .success(let metadata):
...
case .failure:
...
}
}The current identity of a Metaplex instance can be accessed via metaplex.identity() and provide information on the wallet we are acting on behalf of when interacting with the SDK.
This method returns an identity object with the following interface. All the methods required a solana api instance
public protocol IdentityDriver {
var publicKey: PublicKey { get }
func sendTransaction(serializedTransaction: String, onComplete: @escaping(Result<TransactionID, IdentityDriverError>) -> Void)
func signTransaction(transaction: Transaction, onComplete: @escaping (Result<Transaction, IdentityDriverError>) -> Void)
func signAllTransactions(transactions: [Transaction], onComplete: @escaping (Result<[Transaction?], IdentityDriverError>) -> Void)
}The implementation of these methods depends on the concrete identity driver being used. For example use a KeypairIdentity or a Guest(no publickey added)
Let’s have a quick look at the concrete identity drivers available to us.
The GuestIdentityDriver driver is the simpliest identity driver. It is essentially a null driver that can be useful when we don’t need to send any signed transactions. It will return failure if you use signTransaction methods.
The KeypairIdentityDriver driver accepts a Account object as a parameter.
The KeypairIdentityDriver driver accepts a PublicKey object as a parameter. Its a read only similar to the GUestIdentity but it has a the provided PublicKey. It will return failure if you use signTransaction methods.
You may access the current storage driver using metaplex.storage() which will give you access to the following interface.
public protocol StorageDriver {
func download(url: URL, onComplete: @escaping(Result<NetworkingResponse, StorageDriverError>) -> Void)
}Curently its only used to retrive json data off-chain.
This will use URLShared networking. Which is the default iOS networking implmentation. This maybe the most useful call.
This will use return Empty Data object with 0 size.
As mentioned above, this SDK is still in very early stages. We plan to add a lot more features to it. Here’s a quick overview of what we plan to work on next.
- New features in the NFT module.
- Upload, Create nfts to match Js-Next SDK.
- More documentation, tutorials, starter kits, etc.
The SDK heavily inspired in the JS-Next. The objective of this is to have one Metaplex wide interface for all NFTs. If you use the Js-Next sdk this sdk should be familiar.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent