Shopify to leverage blockchain to eliminate counterfeits ...

70+ crypto gateways for your store/business. How to choose and start accepting cryptocurrencies?

70+ crypto gateways for your store/business. How to choose and start accepting cryptocurrencies?
Nowadays cryptocurrencies become more and more popular among retail and service companies all over the world. By our statistics we observe monthly growth of stores, markets, services, websites accepting cryptocurrencies as a payment.
But so far there has not been a high-quality tool that would help you to choose right payment gateway with all necessary functions that you would like to implement into your business.
So, Cryptwerk.com comes to help you!
Our catalogue lists more than 70+ different companies with crypto processing service.
Use this link to enter the gateway directory.
https://cryptwerk.com/companies/payment-gateway/
1. Cryptocurrencies
You must first decide what cryptocurrencies you want to accept.
Use our filters to select those gateways that provide their service with the coins of your choice.
Cryptwerk currently lists 22 most popular cryptocurrencies:
Bitcoin, Ethereum, Litecoin, Bitcoin Cash, Dash, Dogecoin, XRP, Monero, Ethereum Classic, Zcash, Tron, Digibyte, EOS, Qtum, Bitcoin Gold, NEO, Binance Coin, Decred, Verge, Groestlcoin, Bytecoin, Komodo.

https://preview.redd.it/eh44eqye8ze41.png?width=273&format=png&auto=webp&s=84f46f4405daba9923967e6977653ebaca21ac70
You can choose one or several coins, and our website will show you a list of gateways according to your request.
2. Interface
Modern gateways provide various types of services focused on various types of business
Wallet (web or application), ready-made plugins for CMS, various widgets & buttons, POS terminals for offline retailers, sending invoices by email or sms, donation functions.
https://preview.redd.it/0bxttzmg8ze41.png?width=254&format=png&auto=webp&s=239cd34d872377c2ff19edaaf79a74572e8f94fc
3. CMS plugins
This option is very useful for people who are using a Content Management System in their work with the website.
With our filters you can find a gateway with the ready-made solution for your CMS.
Thus, the installation will be very quick and easy!
Just look at the CMS list supported by cryptographic gateways:
aMember Pro, AppThemes, Arassta, bbPress, BIGcommerce, Blesta, BOX billing, CB paid, Checkfront, CS.cart, DJ-Classifieds, Drupal Commerce, Easydigitaldownloads, ECWID, Event espresso, EventBooking, GIVE donations, HikaSHop, HostCMS, HTML5, Imagine, J2 store, Jigoshop, Joomla, LOADED commerce, Magento, ocStore, Opencart, OScommerce, NATS4, NCR, nopCommerce, PaidMembershipsPro, Payplans, phpMySQL, Planyo, Poster, PrestaShop, RedShop, R_keeper, Shop-Script, Shopify, Shopware, SpreeCommerce, SPY, Sylius, TheCartPress, Thirty Bees, Tomato Cart, Typo3 Multishop, VirtueMart, UberCart, uCommerce, Unique free, Waimea business, WCmarketplace, WHMOS, WooCommerce, Wordpress, WP eCommerce, Wpmudev, XCART, ZENcart, 1С.
https://preview.redd.it/cukjy4wk8ze41.png?width=265&format=png&auto=webp&s=e4ef8a9ee89cfd93fb2aedf8290c73bce6df9354
4. Lightning network
Some gateways already use network lightning technology. Here you can filter out the companies that provide this service with Bitcoin and Litecoin.

https://preview.redd.it/3ffrhytm8ze41.png?width=264&format=png&auto=webp&s=1891680a37fcd431bbe32204021590d687bb491e
Using our catalogue and filters you can choose the exact payment gateway that will meet the needs of your business.
Also, here you can see the rating of payment gateways according to our data. The rating depends on gateway popularity among merchants registered on Cryptwerk.com
https://preview.redd.it/yh2p2dun8ze41.png?width=579&format=png&auto=webp&s=77c41d705ebd8f52f22de7d18b491b315850db92
We can mark first 5 companies that are most popular among our merchants.
You can safely use any of these gateways, each of which provides quality service proven by thousands of merchants.
We hope this article will be useful to all merchants who are thinking of starting to accept Bitcoin, Ethereum, Litecoin and other popular cryptocurrencies.
submitted by Cryptwerk to CryptoCurrencies [link] [comments]

My response to recent concerns

Hey all,
I’ve spent some time during my flight back home to discuss in detail the experience in Singapore, what talked about, things the mods and team are working on, improvements that can be made and some other things too. This post has also had input from the other moderators too.
I don’t think any of the mods were massively pleased with the outcome of how we portrayed our time in Singapore during the last update and it certainly didn’t put across all the fantastic things we learnt or discussed while we were there. There was a quick turnaround with the update and with some of us were travelling and heading to other countries for various reasons it wasn’t ideal – anyway let’s begin. P.s. I apologise in advance for the lengthy post.

Education

As most of you are aware there is a rebranding process going on for Request currently, it was really exciting to hear Robbins experience and to see the scope of the project. Request are working with an industry leading full-service digital agency to improve the understandability of Request through educational content.
The current Request website is mainly catered towards ICO investors and hasn’t really changed much since the token sale – when visiting the site, it’s extremely difficult to understand what Request is, how it works and who can it benefit from the platform. One of the goals of the project is to revamp the website to cater for developers, businesses, users, community members, early adopters and investors.
The concept of the blockchain, Request, and its products is daunting for the non-technical audience. While the team know it’s important to cater for developers and other industry professionals having an easy to understand project with easy to consume information is an important step towards adoption.
The Request Hub will also play a critical part in the growth of the Request Network. The new website will have a focus on developers and businesses and pushing them towards the hub and how they can use the funding to help create their projects. Most of you will probably be aware that the dApps + the core protocol are different projects entirely. Internally, this is also the case.
You can see an visual image of the structure here: https://imgur.com/pXF1gEK
The core platform team is responsible for protocol development, things like scaling solutions, data encryption, extensions, features like cross-currency etc. Whereas the dApp teams focus on creating applications built on the Request platform, crowdfunding, invoicing, payments etc. Although this isn’t new information it’s important for sections later in the write-up.

FIAT

This is an excerpt from the 8th June AMA special project update (https://blog.request.network/request-network-project-update-june-8th-2018-ama-special-request-network-now-available-for-5da85547d933) which covers the teams thoughts on FIAT.
Fiat integration is vital for the success of the Request Network for medium to long-term. What we focus on today is making sure the protocol has enough features and a solid developer experience to attract developers to build reliable financial tools on top of the Request Network. The foundation prioritizes its own development goals based on direct feedback coming from the developer community. We receive requests for features that are needed by developers, as their product depends on it.
Today, the main feedback coming from the developer community is to make it easier to use the library, implementation of encryption, cross currency support and adding more cryptocurrencies. Apart from these requests, scalability of the protocol itself and developing extensions such as escrow are also prioritized as it is crucial for adoption of the protocol by developers. The above are our current priorities in development, while we in parallel are researching several fiat integration options mentioned in an update last December.
All of the above bullet points are things the team are actively researching and looking into, we discussed how the Singapore government is looking at tokenizing the Singaporean Dollar and how many more governments in the future will look at taking this route, however this is a long way off.
A decentralised Oracle with Chainlink would be ideal but it’s not ready yet.
Integrations by partnerships with banks / partnering with credit card companies or processors (like Stripe) is incredibly difficult (especially being decentralised) but it’s something the team will actively work on / towards.
Oracle and bank APIs – we discussed several projects here like StellarX, OmiseGo and more – each have their own pros and cons but nothing in the space is really ready for FIAT, some options are close and the team are keeping a close eye on several projects in this space.
There are tonnes of regulatory issues surrounding FIAT and the blockchain, governments are dubious about the blockchain technology and banks are having a tough time getting involved too – even big companies like Binance, Coinbase and Circle still can’t obtain a banking license after many years of trying. The regulatory situation will change, crypto is still a young industry and it will take time for governments to catch up.
Instead of spending time trying to achieve FIAT which wasn’t viable, their time has been spent on far more productive things such as scaling solutions, data encryption, working on various dApps, working with partners, hiring and much more. The better the platform the more impact having FIAT will have when it comes. Yes, not being able to stick to the roadmap isn’t ideal, but the team have realised there are limitations and made the best of the situation.
Would it have been good if the team have been more transparent about FIAT and the issues they faced? Absolutely. Detailed articles about subjects like this do take time, and raise further questions which also take up the team’s time. We want to find a good balance going forward of keeping the team on track and keeping the community informed. We will also work with the team to improve communication for things like this (if they ever arise in the future) and how the mods can alleviate some of the time-pressure if possible.
The team do realise the importance of FIAT, it hasn’t been forgotten and will be something the team will keep on the roadmap – in the future when FIAT is possible we will have a much more mature platform and many use cases live and ready to integrate FIAT.

Marketing

One of the most discussed things over the past months is marketing, this is a very important topic and it’s something that can make or break a project.
As per the ‘Rebranding + Restructure’ section, marketing will be broken down into two different groups, dApps and the core Request platform. The marketing for each of these aspects is very different.
So, why aren’t the team marketing right now? Quite simply – the platform just isn’t ready yet, there isn’t enough value to risk marketing at this stage. This is the same with some of the dApps, they are close, but they still aren’t quite there yet.
In my case if we take a look at the WooCommerce + Shopify plugins, if I go ahead and run a PPC (pay-per-click) campaign before BTC is integrated, then users may leave the site and never return. In this instance I will have lost money as well as a potential customer. This is just one example but it’s the same for other dApps too.
Right now, The team are making active steps towards marking when the platform and dApps are, as well as hiring dedicated marketers.
I do want to say that the team truly understand the importance of marketing, they will market the project and the dApps– it’s critical they do so.
To break it down there are entirely separate game-plans to consider when marketing, the core platform and dApps.
Core Platform (Foundation)
Marketing for the core platform will focus on; educating the community about the platform, educating developers / businesses / potential partners about the Request protocol and how it can be used by / integrated into business workflows.
The rebrand will have a big focus on education and driving adoption of the Request Hub + Fund. In the meantime, we are discussing ways to improve the Request Hub and how we can get more developers involved at this stage, I have covered this in more detail in the ‘Request Hub’ section.
dApps
Each dApp will in essence be its own entity (business) and will act independently of the foundation. Each dApp will have a dedicated team, individual aims and goals, potentially a custom roadmap, a proprietary marketing strategy and much more (everything you expect from a typical business).
Marketing for individual dApps will vary greatly depending on what the dApp is, some will be focussed on B2B, some B2C, some dApps might be a combination of both.

Hiring + strategies to find new devs

The foundation growing at a quick rate and one of the things we discussed in Singapore was hiring and strategies to find new devs.
There are several strategies that the Request team can adopt alongside job advertisements to help entice developers, not only to the foundation but also to the Request Hub. We discussed potentially using freelancers and then hiring if they are a good fit, more engagement from the team with people that contribute to the Request Hub and how the team can help (financially via the fund + time set aside for devs), hackathons with prize incentives, speaking at developer conferences (very important). Some ways of engaging with developers do require the platform / ecosystem to be more mature but we are actively working on making these things a reality. Also, improving the community sentiment will also drive hype which in turn hopefully attracts more developers.

Request Hub + Request Fund

In my opinion one of the best selling points of Request is the Request Hub + Fund. Although there is activity in the hub and some projects have receiving funding it is nowhere near as widely used as it could be. As I’ve discussed in the marketing section, the renewed website will have a big focus on pushing the Hub + Fund.
Aside from the marketing aspect I have also been speaking to teams in the Hub for a while about how the flow for funding can be improved, we have discussed the barrier to entry for the fund (MVP limitations), the turnaround time for responding to funding applications (needs to be quicker), having the team engage more with the Request Hub devs as well as actively helping them with their business needs.
In the future I will also look at creating a suite of tutorials, and potentially workshops, for the Request Hub to help get developers up and running.

Bi-weekly updates

One of the hot topics since returning from Singapore has been the bi-weekly updates, we have been discussing with the team how they can be improved without taking up too much time for the team. There are several things which are actively being discussed:
This will be an ongoing discussion with the foundation, it will take time to refine the bi-weeklys and we also need to find a happy medium that suits both the foundation and the community too.

The Community Managers and our role

The goal as community managers is to firstly ensure that the social channels e.g. Reddit, Discord, Slack and Telegram are a good place for investors, the team and developers – we want to ensure it’s good for open discussions (both positive and negative) and a place where we can educate people about Request too.
As community managers we want to try and stay as impartial as possible, we will help to educate when we can, we’ll shut down any false information and we’ll help alleviate any concerns where possible. We don’t want to take sides, we are simply there to be a bridge between the team and the community.
We want the Request community to be an open place where anyone can discuss what they want, we want to see discussions about good things and bad – we don’t want Request to be a place where negativity is censored. We (the mods) are just normal guys, we love technology, we love the blockchain, we are just investors like all of you, and we want the best for the Request Network.
We are continually improving how we and the team deliver information, but things can still be improved massively – we are already actioning some things to improve communication between the community and the team and we have plenty of other things lined up too.

Roadmap

During the rebrand the website will rework the dynamic roadmap to something potentially similar to Ark (https://ark.io/roadmap), with percentages (or something similar) and a breakdown of each goal on the roadmap. This will help with transparency and also allow the community to track progress more easily.
I’ll cover my perspective on the dynamic roadmap looking from a developers point of view, as a lot of people are still unsure as to why the roadmap has changed and in turn it raises lots of questions.
From a developers point of view.
As a dev it can be incredibly difficult to hit deadlines that are more than a few weeks / over a month or two away, the further away the date the harder it is to estimate + hit deadlines. This is the case for a normal business, but as crypto is insanely fast paced and such a new industry this is even more prevalent.
In the normal development world you typically work in weekly / bi-weekly sprints to produce features in small iterations which contributes to the overall project, at the end of each sprint you re-evaluate the previous weeks and re-adjust timings / resources if necessary – estimating deadlines months in advance is almost impossible.
The biggest issue about committing to a firm date is that crypto adoption is moving at a fast rate, non-blockchain businesses are getting involved with cryptocurrencies and a great platform like Request is an attractive option for them. On-boarding these businesses takes money, expertise and most importantly team resources. The team is growing but for now the time spent with these partners needs to come from somewhere, and unfortunately features can sometimes get affected.
Let's take BTC support - if the team was fully focused on BTC I would have no doubt there would have been no delay. But PwC came along, which took up development resources and, unfortunately, impacted the deadline. Long-term, having PwC onboard will have a more positive effect on the overall Request Network ecosystem. Partnerships won't wait around, Bitcoin support will.
With these partnerships there will be a push for features they want to see. PwC for example, would be focused on the accounting so they would likely be pushing for accountancy related dApps (http://accounting.request.network/) - when the roadmap was first created the team could never predict such a huge entity like PwC would come onboard, so changing focus is sometimes required from a project. Once again, long-term this will benefit Request massively.
From a development perspective changing the roadmap is a fantastic move in my opinion, the team never know what is around the corner and being able to quickly adapt to new opportunities, on-boarding companies are critical for the long-term viability of the network. As the team grow there will be more development resource available to focus on the core platform and partners which will allow the team to better predict features in the future. Once again, I’d like to reiterate things do need improving here, the team can be more transparent, and the roadmap can, and will, be improved.

Summary

The Singapore trip was fantastic, and it was an incredible experience working closely with the team and it was great to see their passion and talent while working away through the week, it’s an excellent work environment too.
Every bit of feedback is incredibly important, please don’t hesitate to get in touch at any time to me or any of the mods, either by Reddit, Discord, Slack or Telegram.
There is a lot of work ahead for the mods and the team, but rest assured we have every single one of your concerns in our scope; the community and the perception you guys have is so important to the team and the project. There are a lot of great things going on that we will continue to improve and lots of things that need changing – it won’t be something that happens overnight but something that will be continuously improving for the entirety of the project – we are dedicated to working hard and improving Request and the community every day.
At the end of all this, actions speak louder than words, and we will take everything into consideration to help ensure Request thrives, we are already in the process of actively making changes.
Apologies for the lengthy post but hopefully this clears some bits up and helps to put across some of the great things we saw in Singapore, if you have any other questions feel free to leave a comment or get in touch privately. Cheers.
submitted by AdmREQ to RequestNetwork [link] [comments]

Community management response to recent concerns.

Hey all,
I’ve spent some time during my flight back home to discuss in detail the experience in Singapore, what talked about, things the mods and team are working on, improvements that can be made and some other things too.
I don’t think any of the mods were massively pleased with the outcome of how we portrayed our time in Singapore during the last update and it certainly didn’t put across all the fantastic things we learnt or discussed while we were there. There was a quick turnaround with the update and with some of us were travelling and heading to other countries for various reasons it wasn’t ideal – anyway let’s begin. P.s. I apologise in advance for the lengthy post.

Rebrand + the Request structure

As most of you are aware there is a rebrand going on for Request currently, it was really exciting to hear Robbins experience and to see the scope of the rebrand. Request are working with an industry leading full-service digital agency to improve Request not only as a brand but as an organisation too.
The current Request website is mainly catered towards ICO investors and hasn’t really changed much since the token sale – when visiting the site, it’s extremely difficult to understand what Request is, how it works and who can it benefit from the platform. One of the goals of the rebrand is to completely revamp the website to cater for developers, businesses, users, community members, early adopters and investors.
The concept of the blockchain, Request, and its products is daunting for the non-technical audience. While the team know it’s important to cater for developers and other industry professionals having an easy to understand project with easy to consume information is an important step towards adoption.
The Request Hub will also play a critical part in the growth of the Request Network, the new rebrand + website will have a focus on developers and businesses and pushing them towards the hub and how they can use the funding to help create their projects. Alongside the rebrand the foundation will undergo a restructure (which ties into the new rebrand). Most of you will probably be aware that the dApps + the core protocol are different projects entirely, although the dApps leverage the Request platform they are treated and handled differently internally at Request.
You can see an visual image of the structure here: https://imgur.com/pXF1gEK
The core platform team are responsible for protocol development, things like scaling solutions, data encryption, extensions, features like cross-currency etc. Whereas the dApp team focus on creating applications built on the Request platform, crowdfunding, invoicing, payments etc. Although this isn’t new information it’s important for sections later in the write-up.

FIAT

This is an excerpt from the 8th June AMA special project update (https://blog.request.network/request-network-project-update-june-8th-2018-ama-special-request-network-now-available-for-5da85547d933) which covers the teams thoughts on FIAT.
Fiat integration is vital for the success of the Request Network for medium to long-term. What we focus on today is making sure the protocol has enough features and a solid developer experience to attract developers to build reliable financial tools on top of the Request Network. The foundation prioritizes its own development goals based on direct feedback coming from the developer community. We receive requests for features that are needed by developers, as their product depends on it.
Today, the main feedback coming from the developer community is to make it easier to use the library, implementation of encryption, cross currency support and adding more cryptocurrencies. Apart from these requests, scalability of the protocol itself and developing extensions such as escrow are also prioritized as it is crucial for adoption of the protocol by developers. The above are our current priorities in development, while we in parallel are researching several fiat integration options mentioned in an update last December.
All of the above bullet points are things the team are actively researching and looking into, we discussed how the Singapore government is looking at tokenizing the Singaporean Dollar and how many more governments in the future will look at taking this route, however this is a long way off.
A decentralised Oracle with Chainlink would be ideal but it’s not ready yet – hopefully we will see Chainlink launch on the main-net soon.
Integrations by partnerships with banks / partnering with credit card companies or processors (like Stripe) is incredibly difficult (especially being decentralised) but it’s something the team will actively work on / towards.
Oracle and bank APIs – we discussed several projects here like StellarX, OmiseGo and more – each have their own pros and cons but nothing in the space is really ready for FIAT, some options are close and the team are keeping a close eye on several projects in this space.
There are tonnes of regulatory issues surrounding FIAT and the blockchain, governments are dubious about the blockchain technology and banks are having a tough time getting involved too – even big companies like Binance, Coinbase and Circle still can’t obtain a banking license after many years of trying. The regulatory situation will change, crypto is still a young industry and it will take time for governments to catch up.
Instead of spending time trying to achieve FIAT which wasn’t viable, their time has been spent on far more productive things such as scaling solutions, data encryption, working on various dApps, working with partners, hiring and much more. The better the platform the more impact having FIAT will have when it comes. Yes, not being able to stick to the roadmap isn’t ideal, but the team have realised there are limitations and made the best of the situation.
Would it have been good if the team have been more transparent about FIAT and the issues they faced? Absolutely. Detailed articles about subjects like this do take time, and raise further questions which also take up the team’s time. We want to find a good balance going forward of keeping the team on track and keeping the community informed. We will also work with the team to improve communication for things like this (if they ever arise in the future) and how the mods can alleviate some of the time-pressure if possible.
The team do realise the importance of FIAT, it hasn’t been forgotten and will be something the team will keep on the roadmap – in the future when FIAT is possible we will have a much more mature platform and many use cases live and ready to integrate FIAT.

Marketing

One of the most discussed things over the past months is marketing, this is a very important topic and it’s something that can make or break a project.
As per the ‘Rebranding + Restructure’ section, marketing will be broken down into two different groups, dApps and the core Request platform. The marketing for each of these aspects is very different.
So, why aren’t the team marketing right now? Quite simply – the platform just isn’t ready yet, there isn’t enough value to risk marketing at this stage. This is the same with some of the dApps, they are close, but they still aren’t quite there yet.
In my case if we take a look at the WooCommerce + Shopify plugins, if I go ahead and run a PPC (pay-per-click) campaign before BTC is integrated, then users may leave the site and never return. In this instance I will have lost money as well as a potential customer. This is just one example but it’s the same for other dApps too.
Right now, The team are making active steps towards marking when the platform and dApps are, as well as hiring dedicated marketers.
I do want to say that the team truly understand the importance of marketing, they will market the project and the dApps– it’s critical they do so.
To break it down there are entirely separate game-plans to consider when marketing, the core platform and dApps.
Core Platform (Foundation)
Marketing for the core platform will focus on; educating the community about the platform, educating developers / businesses / potential partners about the Request protocol and how it can be used by / integrated into business workflows. They will also be marketing the Request Hub and the Request Fund to the devs and businesses.
The rebrand will have a big focus on education and driving adoption of the Request Hub + Fund. In the meantime, we are discussing ways to improve the Request Hub and how we can get more developers involved at this stage, I have covered this in more detail in the ‘Request Hub’ section.
dApps
Each dApp will in essence be its own entity (business) and will act independently of the foundation. Each dApp will have a dedicated team, individual aims and goals, potentially a custom roadmap, a propriety marketing strategy and much more (everything you expect from a typical business).
Marketing for individual dApps will vary greatly depending on what the dApp is, some will be focussed on B2B, some B2C, some dApps might be a combination of both.

Hiring + strategies to find new devs

The foundation growing at a quick rate and one of the things we discussed in Singapore was hiring and strategies to find new devs.
There are several strategies that the Request team can adopt alongside job advertisements to help entice developers, not only to the foundation but also to the Request Hub. We discussed potentially using freelancers and then hiring if they are a good fit, more engagement from the team with people that contribute to the Request Hub and how the team can help (financially via the fund + time set aside for devs), hackathons with prize incentives, speaking at developer conferences (very important). Some ways of engaging with developers do require the platform / ecosystem to be more mature but we are actively working on making these things a reality. Also, improving the community sentiment will also drive hype which in turn hopefully attracts more developers.

Request Hub + Request Fund

In my opinion one of the best selling points of Request is the Request Hub + Fund. Although there is activity in the hub and some projects have receiving funding it is nowhere near as widely used as it could be. As I’ve discussed in the marketing section, the rebrand will have a big focus on pushing the Hub + Fund.
Aside from the marketing aspect I have also been speaking to teams in the Hub for a while about how the flow for funding can be improved, we have discussed the barrier to entry for the fund (MVP limitations), the turnaround time for responding to funding applications (needs to be quicker), having the team engage more with the Request Hub devs as well as actively helping them with their business needs.
In the future I will also look at creating a suite of tutorials, and potentially workshops, for the Request Hub to help get developers up and running.

Bi-weekly updates

One of the hot topics since returning from Singapore has been the bi-weekly updates, we have been discussing with the team how they can be improved without taking up too much time for the team. There are several things which are actively being discussed:
This will be an ongoing discussion with the foundation, it will take time to refine the bi-weeklys and we also need to find a happy medium that suits both the foundation and the community too.

The Community Managers and our role

The goal as community managers is to firstly ensure that the social channels e.g. Reddit, Discord, Slack and Telegram are a good place for investors, the team and developers – we want to ensure it’s good for open discussions (both positive and negative) and a place where we can educate people about Request too.
As community managers we want to try and stay as impartial as possible, we will help to educate when we can, we’ll shut down any false information and we’ll help alleviate any concerns where possible. We don’t want to take sides, we are simply there to be a bridge between the team and the community.
We want the Request community to be an open place where anyone can discuss what they want, we want to see discussions about good things and bad – we don’t want Request to be a place where negativity is censored. We (the mods) are just normal guys, we love technology, we love the blockchain, we are just investors like all of you, and we want the best for the Request Network.
We are continually improving how we and the team deliver information, but things can still be improved massively – we are already actioning some things to improve communication between the community and the team and we have plenty of other things lined up too.

Roadmap

During the rebrand the website will rework the dynamic roadmap to something potentially similar to Ark (https://ark.io/roadmap), with percentages (or something similar) and a breakdown of each goal on the roadmap. This will help with transparency and also allow the community to track progress more easily.
I’ll cover my perspective on the dynamic roadmap looking from a developers point of view, as a lot of people are still unsure as to why the roadmap has changed and in turn it raises lots of questions.
From a developers point of view.
As a dev it can be incredibly difficult to hit deadlines that are more than a few weeks / over a month or two away, the further away the date the harder it is to estimate + hit deadlines. This is the case for a normal business, but as crypto is insanely fast paced and such a new industry this is even more prevalent.
In the normal development world you typically work in weekly / bi-weekly sprints to produce features in small iterations which contributes to the overall project, at the end of each sprint you re-evaluate the previous weeks and re-adjust timings / resources if necessary – estimating deadlines months in advance is almost impossible.
The biggest issue about committing to a firm date is that crypto adoption is moving at a fast rate, non-blockchain businesses are getting involved with cryptocurrencies and a great platform like Request is an attractive option for them. On-boarding these businesses takes money, expertise and most importantly team resources. The team is growing but for now the time spent with these partners needs to come from somewhere, and unfortunately features can sometimes get affected.
Let's take BTC support - if the team was fully focused on BTC I would have no doubt there would have been no delay. But PwC came along, which took up development resources and, unfortunately, impacted the deadline. Long-term, having PwC onboard will have a more positive effect on the overall Request Network ecosystem. Partnerships won't wait around, Bitcoin support will.
With these partnerships there will be a push for features they want to see. PwC for example, would be focused on the accounting so they would likely be pushing for accountancy related dApps (http://accounting.request.network/) - when the roadmap was first created the team could never predict such a huge entity like PwC would come onboard, so changing focus is sometimes required from a project. Once again, long-term this will benefit Request massively.
From a development perspective changing the roadmap is a fantastic move in my opinion, the team never know what is around the corner and being able to quickly adapt to new opportunities, on-boarding companies are critical for the long-term viability of the network. As the team grow there will be more development resource available to focus on the core platform and partners which will allow the team to better predict features in the future. Once again, I’d like to reiterate things do need improving here, the team can be more transparent, and the roadmap can, and will, be improved.

Summary

The Singapore trip was fantastic, and it was an incredible experience working closely with the team and it was great to see their passion and talent while working away through the week, it’s an excellent work environment too.
Every bit of feedback is incredibly important, please don’t hesitate to get in touch at any time to me or any of the mods, either by Reddit, Discord, Slack or Telegram.
There is a lot of work ahead for the mods and the team, but rest assured we have every single one of your concerns in our scope; the community and the perception you guys have is so important to the team and the project. There are a lot of great things going on that we will continue to improve and lots of things that need changing – it won’t be something that happens overnight but something that will be continuously improving for the entirety of the project – we are dedicated to working hard and improving Request and the community every day.
At the end of all this, actions speak louder than words, and we will action take everything into consideration to help ensure Request thrives.
Apologies for the lengthy post but hopefully this clears some bits up and helps to put across some of the great things we saw in Singapore, if you have any other questions feel free to leave a comment or get in touch privately. Cheers.
submitted by DontBlinkETH to RequestNetworkCss [link] [comments]

Buy Bitcoin with Credit Card on Binance HOW to Place a Position, Put a Stoploss, and Close a Position in Binance Shopify + Libra, Vodafone + Bitcoin, BTC Whales, Ripple + Ethereum & No Bitcoin ETF Best Bitcoin Payment Gateway How To Move Your Bitcoin From Gemini To Binance [URGENT] Binance US Block Soon - Alternative Exchanges To Use BINANCE - Buy, Sell, Deposit & Withdraw Cryptocurrency  Buy Ripple  WISDOMified Options Price Calculation Guide in in Binance JEX Exchange, Bitcoin and Cyrpto Currency Lessons How to Day Trade Bitcoin BTC On Binance Step By Step Tutorial Video

Shopify; MyCryptocheckout; BitcoinPay; SpicePay ; Blockonomics. Since blockonomics was officially launched in 2015, merchants across the world have been able to make more sales on their woocomerce website with 1% fee. If you are searching for an anonymous bitcoin payment gateway, blockonomics should be your choice with its low fees, direct to wallet with no ID verification required. I can ... However, consumers who purchase a product containing an NFT can scan that item to verify its authenticity. David Menard, the CEO and Founder of Real Items Foundation, said that a number of skincare, cosmetics, wellness, and fashion companies are currently private beta testing the Shopify plugin. Menard noted that the plugin will officially be released in Q1 of this year. Get 2 binance plugins and scripts on CodeCanyon. Buy binance plugins, code & scripts from $44. All from our global community of web developers. Shopify Plugin For Crypto Currency Payments. What is Cryptohopper? A Summary In its many standard kind, Cryptohopper is an on the internet platform that allows you to make full use of an automated trading bot. This indicates that trades will be put on your part, based on the hidden problems that the bot has been advised to apply. With the Cryptohopper system initially released in 2017, the ... Written by Flora Sun, Director at Binance Labs. Today, Binance Labs would like to introduce our next Binance Fellow, Alexey Miroshkin (a.k.a. hashmap), and his project Knockturn Allee.Alexey is a Grin core developer and and a member of Grin council. He is also part of a Berlin-based cypherpunk cooperative called Cycle42.The goal of Knockturn Allee is to increase the wide adoption of Grin by ... Shopify to leverage blockchain to prevent people from getting cheated. A San-Francisco based blockchain firm named Real Items Foundation leveraged the ability of VeChain blockchain and remotely-hosted application Tokenized Asset Manager (TAM) to enable merchants to generate non-fungible tokens (NFT). When consumers buy any product with an NFT, they will be able to verify the authenticity of ...

[index] [17176] [12350] [19217] [10588] [1273] [20589] [7375] [5148] [5814] [3964]

Buy Bitcoin with Credit Card on Binance

COMPLETE Shopify Tutorial For Beginners 2020 - How To Create A Profitable Shopify Store From Scratch - Duration: 2 ... Use a Debit Card on Binance US to Buy Bitcoin! - Duration: 6:57. Rex Kneisley ... My Second Channel: https://www.youtube.com/channel/UCvXjP6h0_4CSBPVgHqfO-UA ----- Supp... Google Conversion Tracking for your Shopify Store! Easiest Way. Track Google Ads Yash Sareen Easiest Way. Track Google Ads Yash Sareen - Duration: 11:24. Binance is blocking US residence soon. Are you wondering which alternative Bitcoin and Crypto exchanges to use? If so tune in! Become a CryptosRus INSIDER to gain exclusive insight on the market ... How to Short Bitcoin on Binance 125X Leverage Binance Futures Tutorial - Duration: 13 ... I Tried Creating A $100,000 Shopify Dropshipping Business In 7 Days *LIVE* - Duration: 40:17. Justin ... This is a step by step video/tutorial on a simple technique with day trading Bitcoin BTC. Use These links in order to setup your main accounts to start increasing your bitcoin. 1. Set Up Coinbase ... Subscribe to my channel for more videos showing how to create passive income with Cryptocurrency. Start buying Bitcoin now with a FREE account by clicking he... Coinpayments offer plugins for all of the popular web-carts used today such as Shopify, Woo Commerce, Opencart, Magento, and more. It only takes a few moments to download the plugin and start ... Here in Binance JEX, you can trade #Bitcoin Futures, Bitcoin Options, Ethereum Futrues, Ethereum Options, ... How To Create A Shopify Store From Scratch - Duration: 1:42:54. Tobia Wilson ...

#