# Recommended Marketplace Architecture - Fungible Token implementation?

**URL:** <https://forum.flow.com/t/recommended-marketplace-architecture-fungible-token-implementation/1700>\
**Category:** 🏄🏻‍♀️ Cadence\
**Created:** [April 11, 2021, 10:50pm UTC](https://forum.flow.com/t/recommended-marketplace-architecture-fungible-token-implementation/1700 "2021-04-11T22:50:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ericc572](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@ericc572](https://forum.flow.com/u/ericc572)\
**Post date:** [April 11, 2021, 10:50pm UTC](https://forum.flow.com/t/recommended-marketplace-architecture-fungible-token-implementation/1700/1 "2021-04-11T22:50:28Z")

</div>

Hi all, I’m a little stuck in building a marketplace on top of FUSD or FlowToken

The way I understood after doing the tutorials is that in order for a marketplace to be functional, it needs to have two contracts inherit from a FungibleToken AND NonFungibleToken, respectively. A user can then mint NFT’s and sell them on the Marketplace in exchange for FungibleTokens. In the Kitty-items marketplace example, I see there is an example of Kibble tokens that inherit from the FT contract. However, I was wondering if it was possible to directly use FlowTokens and/or the FUSD contract as the implementation for users to buy/sell nonfungibleTokens with. What is the best practice here, if we do not want to create our own FungibleToken implementation?

Are there office hours with the Cadence developer community? I’d love to have the chance to engage and ask questions. Thanks!

---

<div class="post-metadata">

**Author:** ![flowjosh](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/flowjosh/32/362_2.png) [@flowjosh](https://forum.flow.com/u/flowjosh)\
**Post date:** [April 12, 2021, 10:21pm UTC](https://forum.flow.com/t/recommended-marketplace-architecture-fungible-token-implementation/1700/2 "2021-04-12T22:21:43Z")

</div>

You can use the FlowToken or FUSD tokens instead of having to deploy your own. FlowToken addresses are here to import: [Flow Token Contract - Flow Documentation](https://docs.onflow.org/core-contracts/flow-token/)  
and you can get FlowToken on testnet using the faucet: [https://testnet-faucet.onflow.org/](https://testnet-faucet.onflow.org/)

Docs for FUSD are here: [FUSD Stablecoin on Flow - Flow Documentation](https://docs.onflow.org/fusd)

To test with FlowToken or FUSD on the emulator, it is a little bit different. You can sign transactions that mint FlowToken with the emulator service account to mint FlowTokens, but you have to deploy your own FUSD on emulator in order to test with those.

---

<div class="post-metadata">

**Author:** ![bluesign](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/bluesign/32/1359_2.png) [@bluesign](https://forum.flow.com/u/bluesign)\
**Post date:** [April 16, 2021, 2:18pm UTC](https://forum.flow.com/t/recommended-marketplace-architecture-fungible-token-implementation/1700/3 "2021-04-16T14:18:05Z")

</div>

I would suggest reading VIV3 contract [0] and Evolution contract [1] if you are planning to make a marketplace.

[0] [https://flowscan.org/contract/A.c2d564119d2e5c3d.VIV3](https://flowscan.org/contract/A.c2d564119d2e5c3d.VIV3)  
[1] [https://flowscan.org/contract/A.f4264ac8f3256818.Evolution](https://flowscan.org/contract/A.f4264ac8f3256818.Evolution)