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.
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.
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.
- Oracle with Chainlink
- Tokenized currencies
- Integration by partnerships with banks
- Oracle and bank APIs
- Partnership with credit card companies or processors`
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.
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.
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.
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:
- Have more clarity on what developers are working on
- Talking about blockers and potential problems the developers have faced, if things are delayed – why?
- Have an insight into why certain decisions have been made e.g. FIAT, transparency goes a long way here.
- Is it possible for there be previews of dApps or upcoming features?
- Talking about things going on behind the scenes without committing to firm dates / jeopardising anything.
- Can the team promote the Request Hub projects more on social platforms?
- Can we talk about the Request Hub projects? From an outsider’s perspective reading just the bi-weeklys it looks like not much is going on which couldn’t be further from the truth – it's clear there are exciting and innovative things going on behind the scenes and we want to demonstrate that as much as possible in the bi-weeklys.
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.
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.
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.
What is Fuloos Coin and why should we use it? Fuloos Coin
is an open-source digital currency, allowing merchants and users across the globe to send transactions fast and with low fees. We officially released Fuloos Coin on December 1st, 2017.
We are the next digital currency that uses the Scrypt Algorithm to allow users to transact their funds fast and with low fees across the world without delays with the ability to stake your coins to earn interest on your funds. Fuloos Coin
has grown a lot since we started in 2017, reaching other 20,000+ members supporting the community and the development team for the future of the Fuloos
making us the most affordable cryptocurrencie for merchants and users around the world making it easier to pay for services, friends or employees with almost instant transactions.
Our main infrastructure is backed by multiple dedicated nodes to insure our network never goes down and allowing users to use Fuloos Coin
any time of the day providing a secure and reliable environment for merchants with no downtime what's so ever.
Where can I buy Fuloos Coins?
Here's a list of the current exchange platforms that allow you to trade FLS with different cryptocurrencies:
We are hoping to be listed on many more exchanges over the coming weeks to improve the accessibility of purchasing coins and daily trading for Fuloos
Any other questions regarding this? Please, contact one of the team members in one of the social chats we provide.
What is staking?
Staking also known as Proof-of-Stake or POS, is the ability for Fuloos
Coin holders to earn interest on their funds with our inbuilt stake-miner into our desktop wallets which allows our network to run smoothly with our community support by validating transactions or by mining blocks just by keeping your wallet open.
For example, if I had 1000 Fuloos
Coin's and if the transaction's dates have been longer than seven days, I could potentially earn 0.85 Fuloos
Coin's every 10 minutes. Technical Specifications:
- Minimum Stake Age : 24 Hour
- Maximum Stake Age : 7 Days
If you would like to know more information about staking your funds, you can use our own calculator to find out how much you can earn. Proof-of-Stake Calculator
Where can I store my coins?
There are several options on places to store your coins, starting from the exchange platforms which have inner wallets like Stocks.Exchange
. However, the most secure way to store your coins is to keep it in outside wallets. Here’s a list of wallet options to store your coins:
- Official Web-Wallet (Coming soon, beta version released)
- Official Desktop Wallets
- Official Mobile Wallets (Coming very soon, still in development)
- Official Merchant Platform (Will be released within the coming weeks)
Choose the best option that is suitable for you and don’t feel shy to ask us for help when setting up your wallet. Please, understand that your wallet is a source where you store your funds. Take it seriously, use all the available protection methods (backups, 2FA, complicated passwords).
Are there any local communities presented in my native language? Definitely
, Fuloos Coin is a cryptocurrencie with supporters all over the world. Be the first one to hear news in your native language and meet other users in our community!
You can see our community managers via our official team page on our website and also can ask questions in our chats to speak one of the community managers directly, if you have any suggestions for the Fuloos Team or your local community.
Can I use Fuloos Coin as a payment method? Is it possible to spend the coins in a store, shop, hotel, etc.?
Of course, you can purchase items or buy goods/services using Fuloos
. We are currently working on our new merchant platform which will allow online store owners to accept Fuloos
easily using a created plugin by our development team. Popular E-commerce Platforms will be supported:
- WordPress (Woocommerce)
- And many more...
If you are a developer and would like to help create service or integrate Fuloos into your own website, you can use the created PHP Class created by LiteSpeed to make it easier to install and use, there will also be a c++ version released soon for programs integration. https://github.com/LiteSpeedDev/FuloosRPC/
Social Links & Community Chats.
Following our social media and joining our community chats will allow you to keep up to date with the Fuloos
Development and News relating to Fuloos
Partners and Announcements. The Fuloos team is glad to welcome every new user into our community. Join our family to be a part of one of the most prospective cryptocurrencies and enjoy it! Yours truly, LiteSpeed, CryptoKnight & the Fuloos Team.
A reporter from the local news station saw a post of mine about accepting cryptocurrencies and he wants to do a story about small businesses accepting cryptocurrencies tomorrow morning at 9am. Great news but, yikes! A little about us: We've been in business about two and a half years. We (Lost Pines Yaupon Tea) make tea from yaupon, the only caffeinated plant native to North America. When I set our website up I figured we might as well accept bitcoin. It's fun and it lets us tap into a completely different network of people. Since then we've accepted about $325 worth of orders in crypto (worth far more now because we never converted it to USD). We've mostly taken bitcoin, because there's a simple plugin for Shopify that allows us to. We've also taken bitcoin cash 'manually' when it's been offered as payment. I'm far from being an expert in cryptocurrencies, but I have been working in the computer field for a long time so I'm not clueless. Any advice? submitted by
But blockchain-based Shopify plugin is a whole new thing both for the crypto traders/investors and individual consumers. Recently, a piece of news comes into the limelight that explains a San Francisco-based startup “Real Items Foundation” is beta testing a Shopify plugin. It includes blockchain technology to ensure that online shoppers buy the most authentic items only. OpenNode Bitcoin Payment Plugin Launches on Shopify. March 28, 2019. News. OpenNode, a platform leveraging Lightning Network and funded by one of America’s most prominent entrepreneurs and investor Tim Draper, has launched a new Shopify plugin that allows Bitcoin transactions on e-commerce platform. Leveraging the Lightning Network. The lightning network since it was officially revealed last ... One of the big ways that Bitcoin and other cryptocurrencies have been adopted as a mainstream use case has been in the retail industry. While there are still only a select group of companies that are Bitcoin Bitcoin Daily: Shopify Plugin Uses Blockchain For Authentication, SportsCastr Launches Its Own Crypto. By PYMNTS. Posted on January 22, 2020 January 22, 2020 6:27 pm. Share . Tweet ... Shopify Integration Plugin. Accept bitcoin on your Shopify store with BitPay's one-click integration. Integration Requirements. Get started by signing up for a BitPay merchant account. Connecting BitPay and Shopify. Log in to your BitPay merchant dashboard and create an API Token in your BitPay merchant dashboard. Make sure the Require Authentication checkbox is not checked; Use the Token ...
COMPLETE Shopify Tutorial For Beginners 2020 ... WordPress Bitcoin Plugin Usage - Duration: 3:49. Korin Iverson 9,239 views. 3:49. How To Add Coinbase API + Secret Keys - Duration: 2:20. Bitcoin ... Ripple(XRP) Q4 financial reports, Vechain(VET) tested with shopify plugin, livestream recap ----- Check out my other channels: My other ch... The real-time build of https://jigawatt.co, an online shop that accepts bitcoin lightning payments, using OpenNodes WooCommerce plugin. On https://jigawatt.co you can support BTCIOT by buying ... http://ytwizard.com/r/7tNDmm http://ytwizard.com/r/7tNDmm Bitcoin And Crypto-Currencies For Shopify Store Owners What Bitcoin Is, Why Consider Accepting It A...