Weave Code
Platform Marketplace Laravel Package
enjin/platform-marketplace
Enjin Platform Marketplace is a Laravel package that adds NFT marketplace capabilities to Enjin Platform applications. It includes listings, auctions, offers, sales, and wallet integration, helping developers build blockchain-backed marketplaces with familiar Laravel workflows.
A package for integrating the Marketplace into the Enjin Platform.
Frequently asked questions about Platform Marketplace
- What is enjin/platform-marketplace used for?
- It is a Laravel package that adds NFT marketplace capabilities such as listings, auctions, offers, sales, and wallet integration to applications already running the Enjin Platform. It extends platform-core's domain model and GraphQL schema rather than providing a standalone marketplace. If you are not on the Enjin stack, it will not drop into a generic Laravel application.
- Can I use enjin/platform-marketplace in a standard Laravel app without Enjin Platform?
- No, effectively not. It is a satellite module to enjin/platform-core and depends on platform-core's NFT and token definitions, collections, wallet ownership, and GraphQL schema. Using it outside Enjin Platform means onboarding the entire Enjin Platform stack, including chain configuration, RPC connectivity, key management, and indexing. That is a quarter-scale effort, not a simple package install.
- How do I install enjin/platform-marketplace?
- Install it with Composer using composer require enjin/platform-marketplace, register the service provider, publish configuration and migrations, and extend the GraphQL schema. You also need to map your catalog to platform-core NFT and token models and wire marketplace listings to existing asset and ownership tables. Audit the published migrations for collisions and plan a staging or testnet rehearsal before production.
- Which Laravel, PHP, and enjin/platform-core versions are supported?
- The package is tied to the Enjin Platform stack and is expected to track platform-core releases closely, but public documentation on supported PHP, Laravel, and Lighthouse versions is thin. Check the package's composer.json constraints and release history before committing. Because version lockstep with platform-core matters, pin both packages, review whether migrations are reversible, and test upgrades in staging.
- What marketplace features does enjin/platform-marketplace include, such as fixed-price listings, auctions, offers, and royalties?
- The overview names listings, auctions, offers, sales, and wallet integration. The technical assessment warns that the exact scope, including bundles, fees, and royalties, is not clearly documented, and some primitives may be stubbed rather than implemented. Audit the GraphQL schema and migrations to confirm what is production-ready before building product features on it.
- Where does settlement happen with enjin/platform-marketplace: on-chain escrow, custodial wallet, or off-chain ledger?
- The package adds marketplace concerns including settlement, but the public materials do not clearly specify whether settlement uses on-chain escrow, a custodial platform wallet, or an off-chain ledger. You need to confirm this in the code and platform-core integration before handling real funds. Treat blockchain-adjacent failure modes such as double settlement, stuck listings, and stale ownership after transfer as financial risks.
- Which networks does enjin/platform-marketplace support, and is there a local test mode for CI?
- It targets the Enjin ecosystem through platform-core's chain configuration, with Enjin Matrixchain, Canary, and testnet being the relevant networks to confirm. The available documentation does not clearly describe a local or simulated mode for CI. Before mainnet exposure, require a staging or testnet rehearsal and verify RPC connectivity, wallet and key management, and indexing behavior.
- Is enjin/platform-marketplace production-ready and well maintained?
- Adoption signals are weak: no stars, no dependents, and no visible community validation, which usually correlates with thin documentation and untested edge cases. Maintenance appears tied to a small Enjin core team rather than a broad contributor base. Treat the package as pre-production maturity until you can point to known production deployments and test coverage.
- Does enjin/platform-marketplace include a UI, or is it API-only?
- It is a Laravel Composer package that extends the Enjin Platform GraphQL schema with marketplace operations, and the overview does not describe a shipped frontend. Expect to build your own UI or admin tooling on top of the GraphQL API. Confirm the exact GraphQL surface, including queries, mutations, and types, by inspecting the schema extension.
- What are the alternatives to enjin/platform-marketplace for building an NFT marketplace in Laravel?
- If you are committed to Enjin Platform, the main alternative is implementing marketplace logic directly against platform-core instead of adding this package. If you are not on Enjin, look at standalone NFT marketplace libraries or build listings, offers, and settlement around your own chain SDK and database. The package is only a fit when you already run Enjin Platform core with Lighthouse GraphQL.
Weaver
How can I help you explore Laravel packages today?