-
Notifications
You must be signed in to change notification settings - Fork 912
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
…in (#260) * Bump color-string from 1.5.4 to 1.6.0 Bumps [color-string](https://github.com/Qix-/color-string) from 1.5.4 to 1.6.0. - [Release notes](https://github.com/Qix-/color-string/releases) - [Changelog](https://github.com/Qix-/color-string/blob/master/CHANGELOG.md) - [Commits](Qix-/color-string@1.5.4...1.6.0) --- updated-dependencies: - dependency-name: color-string dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> * Bump prismjs from 1.23.0 to 1.24.1 Bumps [prismjs](https://github.com/PrismJS/prism) from 1.23.0 to 1.24.1. - [Release notes](https://github.com/PrismJS/prism/releases) - [Changelog](https://github.com/PrismJS/prism/blob/master/CHANGELOG.md) - [Commits](PrismJS/prism@v1.23.0...v1.24.1) --- updated-dependencies: - dependency-name: prismjs dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> * Bump path-parse from 1.0.6 to 1.0.7 Bumps [path-parse](https://github.com/jbgutierrez/path-parse) from 1.0.6 to 1.0.7. - [Release notes](https://github.com/jbgutierrez/path-parse/releases) - [Commits](https://github.com/jbgutierrez/path-parse/commits/v1.0.7) --- updated-dependencies: - dependency-name: path-parse dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> * Add showcase guideline proposed in #176 (#235) * Added The Galgos NFT project (#163) * Add Python Module (#220) * Add Python Module * Add mention of cardano-wallet backend * Remove tags * Remove getstarted link * fix urls and native token sentence (#240) * fix: backslash missing from code example (#246) * removed duplicate for copy command (#244) * IO Fix (#245) Co-authored-by: Priyank * Update get started with developer community (#249) * august developer spotlight article mercury (#256) Co-authored-by: Kevin Cislak <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Tommy <[email protected]> Co-authored-by: thegalgos <[email protected]> Co-authored-by: Michał Sałaban <[email protected]> Co-authored-by: cislakk <[email protected]> Co-authored-by: Ari V <[email protected]> Co-authored-by: Jackson Barnes <[email protected]> Co-authored-by: Kevin Cislak <[email protected]>
- Loading branch information
1 parent
67a4d74
commit fd4ce3d
Showing
11 changed files
with
8,309 additions
and
8,364 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,77 @@ | ||
--- | ||
slug: 2021-08-23-august | ||
title: "August Spotlight Interview" | ||
author: Cardano Foundation | ||
author_title: Developer Spotlight | ||
author_url: https://github.com/cardano-foundation | ||
author_image_url: https://avatars.githubusercontent.com/u/37078161?s=200&v=4 | ||
tags: [payment, interview] | ||
description: "August Spotlight Interview" | ||
image: https://developers.cardano.org/img/og-developer-portal.png | ||
--- | ||
|
||
![title image](/img/devblog/mercury-logo.jpg) | ||
|
||
For the August edition of the Developer Spotlight article, we will interview [Adam Dean](https://twitter.com/adamKDean), the primary developer of [Mercury for WooCommerce](https://github.com/cardano-mercury/cardano-mercury-woocommerce). | ||
<br /> | ||
|
||
**_Hey Adam! Happy to connect today and learn more about the Mercury for WooCommerce project! Can you tell us more about the project and what is the problem that you were addressing?_** | ||
|
||
With Cardano Mercury for WooCommerce, my goal was to make a simple and accessible solution to bridge traditional e-commerce with the Cardano Blockchain. WooCommerce is one of the largest open-source e-commerce platforms in the industry. So it was only natural to create a similarly open-source, fee-free payment gateway to bridge Cardano to WooCommerce. One of the most significant barriers to entry in the cryptocurrency industry is the need to trade back and forth between fiat and crypto. Mercury aims to eliminate that friction point by allowing merchants and shoppers to transact directly with one another with the currency of the future. | ||
|
||
<br /> | ||
|
||
<!-- truncate --> | ||
|
||
|
||
**_What are the most important things about Mercury for WooCommerce?_** | ||
|
||
Probably the most important point about Mercury for WooCommerce is that there are zero fees, zero accounts required, and zero tracking. When developing Mercury, the goal was not to profit but to help drive adoption and utilize the blockchain to connect customers directly to vendors. The software is relatively simple and easily auditable. It aims to use free or low-cost APIs (including the amazing Blockfrost Cardano API by Five Binaries) and services** to minimize the financial impact to vendors. | ||
|
||
<br /> | ||
|
||
**_Going forward, how will Mercury make an impact in the crypto space or on the world?_** | ||
|
||
I hope that Mercury will open the door to much larger, mainstream adoption of Cardano (and cryptocurrencies in general) through normalization. For example, suppose we can normalize the usage and transact cryptocurrencies as currency rather than simply a store of wealth mechanism. In that case, we can drive greater adoption by making safe, secure, and auditable transaction history available to vendors and shoppers worldwide. | ||
|
||
<br /> | ||
|
||
**_What are your accomplishments so far, and what are you most proud of?_** | ||
|
||
To date, I’m most proud of having been able to release and open source the code for Mercury via GitHub to the Cardano and WooCommerce community without the need for funding and simply working in my spare time. Of course, there are many features and improvements I’m eager to make to the code and looking forward to ongoing development for the foreseeable future. | ||
|
||
<br /> | ||
|
||
|
||
**_Why should people choose to use Mercury? What are the advantages over its competitors?_** | ||
|
||
To be honest, there are no true competitors to Mercury that I’m aware of at this time. No Middle Man for WooCommerce is another open-source plugin that offers a host of cryptocurrency options without fees or middlemen. However, the Cardano integration for No Middle Man has not been updated since the Byron era. I view No Middle Man as a spiritual predecessor of Mercury and thank the contributors of that project for their open-source work. | ||
I believe that people should choose their financial freedom, which is why merchants should decide to use Mercury. With no fees and no hassle, it’s a no-brainer for merchants to choose to accept Cardano (ada) payments on their website quickly and easily and thereby enable the financial freedom of their customers. | ||
|
||
<br /> | ||
|
||
**_Tell us about your team. Who are the people behind Mercury?_** | ||
|
||
I am the primary developer of Mercury for WooCommerce. I have been a Cardano stake pool owner/operator since the ITN (Ticker: BUFFY) and have always strived to support the Cardano community in every way possible. This includes countless hours spent helping fellow SPOs in public and private Telegram chats, development, and contribution to community tools including simpleLiveView/CNTools gLiveView, Python Slot Leader Log script, Leader Logs Sigma API, development of the first Cardano on-chain voting mechanism (utilizing transaction metadata), and most recently Cardano Mercury for WooCommerce. | ||
|
||
The testing and development of Mercury for WooCommerce would not have been possible without the feedback, brainstorming, and testing contributions of [Kyle Solomon](https://twitter.com/ADAFrog_Pool) (Adosia IoT, Heidrun, spacecoins, FROG stake pool) and Latheesan Kanesamoorthy (primary developer and co-founder of [Tokhun.io](https://tokhun.io/), Heidrun contributor). | ||
|
||
Special thanks to JP Birch [(MADinArt)](https://twitter.com/MADinArt3) for his help developing the Mercury logos and branding and Marek Mahut and the team at [Five Binaries](https://twitter.com/fivebinaries) for the amazing Blockfrost API, which has helped make Cardano integrations like Mercury a painless and straightforward process. | ||
|
||
<br /> | ||
|
||
**_Which partnerships have you engaged so far, and which ones are the most impactful?_** | ||
|
||
The most impactful partnership to date has been with [Crypto Swag](https://twitter.com/CryptoSwagio), the first e-commerce merchant to implement Mercury into their [website](https://crypto-swag.io). It’s one thing to test things in a testnet environment and a completely different level when you officially “go live.” | ||
I have discussed implementing Mercury with several other WooCommerce small business owners and website developers and am excited to increase the use of Mercury as time goes on hopefully. | ||
|
||
<br /> | ||
|
||
**_Thank you for your time! Do you have anything else to add?_** | ||
|
||
I’d like to add my thanks to the entire Cardano Community; keep being awesome. And thanks to the Cardano Developer Portal for choosing Mercury as a featured project! | ||
|
||
<br /> | ||
|
||
** Mercury currently requires at least a Blockfrost Free-Tier API key as well as a free or paid Currency Converter API key if the storefront is using a currency other than U.S. Dollars (USD). | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.