A round-up of Enjin's development activity for the last two weeks.
Another feature-packed development update is upon us and we're excited to share some of the progress we've made so far!
In this bi-weekly update, we will be covering:
- NFTio: The newest and most cutting-edge NFT marketplace.
- Enjin Wallet: The only crypto & NFT wallet you need.
- Enjin Tooling:
a. The Enjin Platform
❗ Any screenshots in this article are subject to change pending further development.
What is NFT.io?
NFT.io is the next marketplace for all NFTs, with an awesome branded domain. NFT.io includes all of the basic functionalities found in any NFT-related marketplace and the ability to work with Efinity in the future. It not only has excellent features, but it also has an easy and friendly user interface and user experience.
This week's update focuses on additions and improvements to the beam process for Efinity on NFT.io. The following updates detail these changes:
- Improved beam creation process;
- The NFT.io development team has upgraded the beam creation process in order to make it easier & simpler for creators.
- Added the ability to pause beams;
- Creators are now able to pause the distribution of Enjin Beams even after they have been published.
- Added 3D model support for tokens, collections & beams;
- NFT.io will now provide full support for 3D models when creating tokens, collections & beams!
- WalletConnect support;
- NFT.io has added WalletConnect support, allowing users to connect their blockchain wallet with native WalletConnect support to the marketplace seamlessly.
- Beam statistics page design update;
- The design of the Beam statistics page has been refreshed to improve the overall user experience and make it easier to navigate.
- Quality-of-life improvements.
📱Enjin Wallet 2.0
What is the Enjin Wallet?
The Enjin Wallet application (available for Android and iOS) is the next-generation crypto and NFT mobile app that enables you to store, send and sell your NFTs, in addition to using the Enjin Wallet just like any other cryptocurrency wallet application.
- Enabling signing proof on the Enjin Platform;
- This upcoming feature will enable users to sign messages on the Enjin Platform using their Enjin Wallet to scan a QR code. When prompted, the wallet will suggest signing the message.
- New design of Collectibles UI;
- The Collectibles page will undergo a complete rework to make browsing and sorting your favorite collectibles easier.
- Optimized loading of wallet balances;
- The Enjin Wallet development team is working to improve how balances load in the wallet, resulting in faster loading times.
- Quality-of-life improvements for both iOS and Android wallet apps.
🛠️ Enjin Tooling
This section is broken down into 3 categories:
- The Enjin Platform
- Enjin SDKs
- Enjin Beam
📖 The Enjin Platform
What is the Enjin Platform?
The new Enjin Platform is a package that enables developers to implement blockchain integration more quickly. With it, game developers can perform blockchain actions without worrying about encoding or signing transactions or understanding specific blockchain technical details.
- Improved transaction record updates after recovery;
- We have made improvements to ensure that transaction records are accurately updated after a resync, such as when the blockchain worker reconnects after a temporary disconnection.
- Upgraded AMPPHP library version.
- The minimum version of the AMPPHP library has been increased to a later revision, which brings various improvements and fixes.
- Fixed issue with Graphql GetWalletQuery not returning relationships;
- The GetQWalletQuery previously had a problem where it did not return relationships correctly, but this issue has now been resolved.
- Added support for Fuel Tanks Codec types;
- We have added support for the new Fuel Tanks blockchain codecs, which expands the range of blockchain assets that can be used on our platform.
- Quality-of-life improvements.
What is Enjin Beam?
Beam is a first-of-its-kind QR-powered blockchain asset distribution service.
With Beam, you can tailor the rewards you send to suit your target audiences and marketing objectives, such as gaming assets, branded collectibles, gift cards, discount codes, early access, and more.
Beam QR codes can be published via any visually accessible medium—from social media networks, websites, ads, and videos to flyers and presentations, and within apps or games.
- Support integer ranges and file upload for tokenId for CreateBeamMutation ;
- We have introduced new features to the CreateBeamMutation function that allow for more efficient and flexible handling of token IDs when creating new Beams. These features include support for integer ranges and file uploads for the tokenId parameter.
- To achieve this, we have implemented a new data type called "Integer Range" which enables users to specify a range of integers using a special format. For instance, to create 10000 tokens with sequential IDs starting at 1, you can simply supply the range as "1..10000". Additionally, we now accept an array of these Integer Ranges in the Beams token ID input, such as ["1..100", "115", "120..150", "155", "178"], allowing for greater flexibility in specifying token IDs.
- Moreover, we have enabled the platform to accept a file upload containing a list of Integers and Integer Ranges. This allows for the input of millions of tokens via a file, where each ID or ID range (in the above format) is listed per line.
- These updates enhance the usability and efficiency of the CreateBeamMutation function when dealing with a large number of tokens.
- Resolved cache count synchronization issue in case of ClaimJob failure;
- We addressed an issue related to the cached count of claims, which was getting out of sync when a ClaimJob failed and was not added back to the claimable pool.
- Rectified the problem of ignoring claimQuantity for CreateBeamMutation;
- The CreateBeamMutation was disregarding the Claim Quantity field when computing the total cached claim count. This was particularly important when dealing with fungible tokens that could be claimed more than once for a single token ID.
- Fixed pagination cursor malfunction in paginated queries;
- Some Beam queries were not properly resolving the pagination cursor, which caused only the first page of results to be returned. We have resolved this issue.
- Update Beam code attribute validation length to 1024;
- We have increased the beam code character limit validation check when claiming beams to support longer single-use codes.
- Support existing beam claim flow for single-use beam codes;
- Harmonized the claim flow for single-use beams with the existing method used for multi-use beams, to enable claiming both types of beams from just the code itself, without necessitating any modifications to client wallet apps.
- Fixed an issue with creating Beams containing more than one token definition.
- We resolved a scenario where the CreateBeam mutation was not handling multiple token definitions correctly, resulting in some token ID claims not being created.
💬 From the Team 💬
That concludes this edition of our bi-weekly development update! Keep an eye out for the next one in two weeks. We’ll see you then!
If you have any questions, concerns, or feedback, please contact us through our support team.
Looking for more developer material? Learn more below:
- Our technical documentation: https://docs.enjin.io
- Our other bi-weekly development updates: https://enjin.io/blog-tags/developers
- Our developer discord hub: https://discord.com/invite/qVA6uDr2f8
- Our help centre: https://enjin.io/help
- Follow us on Twitter: https://twitter.com/enjin
Get the latest news about Enjin tools.Sign Up
Thank you! Please check your email.
Oops! Something went wrong while submitting the form.