Dear Community, We are taking the time to write today, to explain how to setup a server for the testnet V2.

The process is almost the same as the mainnet, and you will be able to follow the mainnet tutorials to setup this server, however this article will tell you during the tutorials what to do differently.

Server Setup

First you will need to follow this tutorial

https://docs.xcash.foundation/dpops/server-setup

their are no changes to this, although their is a note. You will need certain ports open on the server. Their is a firewall included that opens these ports, however some server companies force you to declare open ports on their GUI on their dashpanel as well. You can use an online tool to confirm after setup if your ports are open.

For mainnet you need the following ports open: 18280,18281,18283 (possibly 80 if running shared delegate)

For testnet you need the following ports open: 18280,18281,18283,18286 (possibly 80 if running shared delegate)

What is 18286? this is another empty wallet for turbo tx queries that gets generated when you install. The key is never shown to you at the final summary page, as your not suppose to ever use this wallet. Please do not send xcash to that wallet on port 18286 as its open to the internet. The purpose of this wallet is to expose the xcash-rpc-wallet commands for each delegate to the internet (the non safety concerning ones) this way the merchant tool for turbo tx can query and verify quick tx.

Install The Node

Next you will need to follow this tutorial

https://docs.xcash.foundation/dpops/node-installation

Here are the changes:

https://docs.xcash.foundation/dpops/node-installation#installer-script

for this part use this command instead of the one given

source <(curl -sSL https://raw.githubusercontent.com/X-CASH-official/xcash-dpops/remote-data/scripts/autoinstaller/autoinstaller.sh) && sudo systemctl stop xcash-dpops

Set The Start Time

Now its time to set the start time. If your started the testnet with us at launch date, you will be familiar with this process.

#1 Change the start time and date (5PM Paris time, January 16, 2023)

sudo nano /lib/systemd/system/xcash-dpops.service && sudo systemctl daemon-reload

On the line:

ExecStart=~/xcash-official/xcash-dpops/build/xcash-dpops --block-verifiers-secret-key <BLOCK_VERIFIER_SECRET_KEY>

add the flag -- start-time 123 0 16 15 56 at the end of the line.

The line should look like :

ExecStart=~/xcash-official/xcash-dpops/build/xcash-dpops --block-verifiers-secret-key <BLOCK_VERIFIER_SECRET_KEY> --start-time 123 0 16 15 56

#3 Restart DPOPS

sudo systemctl restart xcash-dpops && journalctl --unit=xcash-dpops -n 100 --follow --output cat

Register Delegate

Next you will need to follow this tutorial

https://docs.xcash.foundation/dpops/register-delegate

There are no changes

Voting and Conclusion

Note if your going to vote and following https://docs.xcash.foundation/dpops/vote-and-staking make sure you use the old mainnet syntax of voting (without the extra amount|all parameter) as its not implemented until we start the testnet minting process

Once you setup the server just view the logs (journalctl --unit=xcash-dpops -n 100 --follow --output cat) to make sure it says “Waiting for the specific start time”, and wait for the testnet to start. We look forward to testing the various features of the testnet V2 with the community.

Testnet V2 — Test 1 Server Setup was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

Dear Community, We are taking the time to write today, to announce what we are going to be testing on the testnet V2. The snapshot has just happened almost about 3 hours ago!!! I want to thank everyone that is still interested in the project and supporting the testnet, as we will have many fun new features to try out on this testnet cycle.

Code Link

Here is the code link for the changes to xcash on this testnet as of now. We will use the “remote-data” branch of both repos:

https://github.com/X-CASH-official/xcash-core/commits/remote-data
https://github.com/X-CASH-official/xcash-dpops/commits/remote-data

Non Protocol Changes

Before we can start testing new protocols, we need to test many DPOPS enhancements and improvements made by the community and the team. These are already in the code and will be running day 1 when the first block is created. These include:

Various upgrades to work with Ubuntu 22.04 (the new LTS).
Various improvements to how networking code works.
Performance improvements on certain functions of the code.

We will run this for about a week or two to make sure its stable and that we have enough participants.

Protocol Changes and Additions

Once this is finished we will start testing the new protocols and features of xcash and xcash dpops. These will include (in this order we will test them):

DPOPS Split Balance Voting

Xcash always listens to the community, and tries to adapt the product to what the community wants. I personally heard multiple community members over the year ask for this specific feature. This will allow one to now vote for one delegate but only allocate a certain amount of the wallet to them, and keep the other part for spending trading etc. The wallet will know when you send a tx to only use the xcash marked as “savings” not the xcash marked as “staking”. When the “savings” xcash is 0, the wallet will not be able to send any xcash until you clear the marks on the wallet using a new command.

It sounds a little complicated but is really simple.

Old commands for vote and revote:

vote <delegates_name|delegates_public_address>
revote

New commands for vote and revote:

vote <delegates_name|delegates_public_address> <amount|all>
revote <amount|all>

with the new command “clear_staked_balance” that will remove all marks and allow one to use any previous staked amount for sending. Note it will not remove the vote, but will just remove the marks so one can send from the staking xcash (and will break the reserve proof like voting in version 1)

Note this will not currently work for voting for multiple delegates from the same wallet, but this innovation allows for this to happen at a later date once this first production is ready. This just allows one to not have to make 2+ wallets for their staking and spending xcash.

Turbo TX

These are tx that take a few seconds to confirm on the network. Using our unique blockchain structure of DBFT and UTXO unspent system, we have possibly created a system for quick tx on our network, that can be confirmed through the delegates using a tool. This will be very important for merchant applications especially in person stores as users can pay for items in seconds with full verification from the merchant that their can be a reversal. For those that know about RBF tx on bitcoin style blockchains, this system is superior to it and eliminates all of the risk.

Do these replace the instant payments we saw in a video long ago? No its a enhancement as we can have layer 1instant payments, and layer 2 instant virtual payments as seen in the video. Those are still a work in progress.

A rough draft of the documentation from my internal setup can be found here https://docs.xcash.foundation/turbotx/get-started as this will give more details about what this protocol is (RBF vs this) and the user/delegate interaction process. (the theory of innovation can be found at https://docs.xcash.foundation/turbotx/introduction)

Xcash Namespace Protocol / Public TX 2.0

We have talked about this one in the past, but it essentially a namespace service run by the delegates. A user can register a namespace and this will automatically include .xcash, .sxcash and .pxcash extensions (and any others we develop in the future). Users will then be able to use these in different ways:

.xcash — give this to a user (instead of your public address) to have them be able to send payments to you.

.sxcash — give this to a user to have them be forced to send you a private tx.

.pxcash — give this to a user to have them be forced to send you a public tx.

A rough draft of the documentation from my internal setup can be found here https://docs.xcash.foundation/remotedata/get-started as this will give more details about what this protocol is and the user/delegate interaction process.

Whats Next?

Besides reading the documentation drafts to familiarize yourself with the new protocols, on Monday December 5, 2022 we will post an article stating how to setup your server. If your planning on participating black Friday is a great time to look into getting a server (any Ubuntu 18.04 and up will work including 22.04). I will use the time between Nov 21 and December 5, to write this tutorial and setup the testnet and seed nodes, and fix any remaining problems if their are any that appear. The testnet is still scheduled for January 2 as of now, but stay tuned to all of the articles if that changes for any reason.

We look forward to testing the various features of the testnet V2 with the community.

Testnet V2 — Test 1 Information was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

Dear Community,

We are taking the time to write today, to announce the new testnet schedule and reward structure for the Testnet V2.

As we discussed in the beginning of the year, we will have a refresh of the testnet about every six months and will have different things to test during every version of the testnet.

For the next testnet (V2) we will test many things, such as Ubuntu 22.04 compatibility and many community xcash dpops improvements on github. We also have two protocols and one new DPOPS voting feature to test. We will make a separate announcement on these once the snapshot has taken place.

The testnet snapshot will be at block height 980000 which is estimated to happen around November 21, 2022 that is about 4 weeks from today.

The testnet will then start producing blocks on January 2, 2023 that is about 10 weeks from today and 6 weeks from the snapshot.

This will give about 4–5 weeks (6 weeks but will take a week or two for me to setup seed nodes and make sure everything is working) for everyone to setup their delegate and vote after the snapshot has taken place. We will detail the changes and all protocols we will test in the testnet V2, the same time the snapshot takes place, in another article.

This way everyone has the full schedule of what will be tested for the next months and can decide if they want to participate in the testnet V2. We have set the dates to be around the holidays and to give enough time for anyone who wants to participate to setup their server and ask any question they might have.

How To Prepare For The Snapshot

You will need to have any xcash you want to be cloned onto the testnet in a wallet you have the private keys for (not xbank or exchanges and not wxcash) only paper, mobile, CLI and GUI would be supported.

QUESTION: I already have a mainnet delegate, and a voting wallet with my xcash, can I use the same setup on the testnet?

Yes. At this point since DPOPS is on mainnet and deemed secure it should be fine to reuse your data. Of course their is no guarantee some kind of bug in the code or testnet code will exist that allows a testnet participant to view sensitive data, but we are not too worried about this, and will be using our seed nodes (wallet and VRF keys) on the mainnet for the testnet as well.

We also suggest you start looking for what server you might want to use, this way you are ready after the snapshot to setup and vote or have people vote for you. The same requirements for xcash dpops will work, and we will support and encourage to use Ubuntu 22.04 (the latest LTS)

New Testnet Reward Structure

Its important that we have the full testnet amount and full participation of the community (50 servers), to test these new protocols. These will require everyone to be active and fully engaged. Because of this, the new structure of rewards will be the following:

The first block of each day in the month (according to UTC time), will be worth 300,000 mainnet xcash. This has been decided as the best way to ensure participation each day from the community, and the fairest way to have the contest. It also adds some excitement each day, as you have a new chance each day to win!

This will be easy to log as we all will have logs of this on our xcash dpops servers. Everyone can verify with the following terminal command:

journalctl --unit=xcash-dpops -n 1100000 --output cat | grep -A 18 "00:00:20 UTC"

This has been chosen as the best way for now to do the “contest” because it is random and the VRF system can pick the winners. It also does not take any previous participation in to consideration, but at the same time rewards constant participation.

The xcash will be sent to the test delegates public address on the mainnet, sometime in the following month (so make sure to back these up when installing your testnet server at the print out of details at the end of the installation)

We are looking forward to the next testnet cycle (testnet V2) and hope that everyone is as excited as we are to test the next protocol.

Testnet Refresh V2 was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

Intro

We understand that most users value convenience and simplicity above all else, and to increase the user amount the typical user’s preferences must be considered.

Two things must be achieved;

1. the user must intuitively understand how to operate the product;
2. the user must be able to use the product on platforms where they already feel familiar.

X-Payment bridges the gap between complexity and consumability, and we now expand it out of Discord and onto your next favorite platforms.

Enter X-Payment on Twitter

From October 3rd, you’ll be able to send and receive XCASH in a way you’ve never experienced.

Instant X-Payment transactions

As an off-chain layer of the X-Cash native chain, X-Payment can process on-platform transactions (Txs) independent of our block time. This means that Txs are transmitted instantly between X-Payment users.

Top Tips

The Leader board located under the Explore tab gives you access to statistics to see who is leading the tipping game, among other vital statistics.

Use on Discord, Twitter, and more to come.

We all have our platform preferences, and Twitter is the favorite of 206 million daily users. X-Payment sits on top of its integrated platforms to give you the best experience where ever you call home.

X-Payment enables a deeper level of cross-platform synergy:

Use cases

1. On Twitter you can now promote your E-Sports tournament, publicly incentivize people to join through Twitter Tips, then through Discord, you can create a Merchant (monetized) tournament registration role for contestants, and finally, send the winners their prize through Discord or Twitter.
2. Tip your favorite digital artist on Twitter to promote their work, and likewise receive tips from your Twitter patrons.
3. Donate to social movements to help alleviate the social issues you care about, and likewise receive funding to start your own social movement.
4. Grassroots fund an indie game developer to fund their development roadmap, and leveraging the power of Twitter your community won’t miss out on the opportunity to support you. The Dev doesn’t even need a Twitter account to receive XCASH from X-Payment.
5. All of the existing X-Payment use cases including the Merchant System.

Note: The combination of the integrated platform’s features with X-Payment, makes the use cases as endless as your imagination.

Get started

To start you need to have some XCASH currency, an X-Payment platform account, and of course a Twitter account :-).

Creating and funding an X-Payment account.

1. Login to the X-Payment platform using your Twitter account.

1. Select the appropriate Deposit wallet from the drop down box. In this case, we select Twitter wallet. There is no difference between wallets, naming is only for your tracking and association. You can use the copy feature to click on the address and it will be copied into your device’s clipboard. Same for payment id/deposit id.

1. Make a deposit. (Please use caution as with any transfer and re-check entered payment id and hot wallet address as your deposit is likely to be lost if incorrect data is entered. Alternatively, if you’re using a mobile wallet you can use the generated QR code X-Cash team is not responsible in case of a “mistake”.
2. Wait for XCASH to arrive. Processed deposits will be marked in the history of deposits and the balance of the Twitter wallet updated (NOTE: the platform auto checks every 5th+1 minute inside an hour. Please reach out to us if the deposit is not processed within 1 hour. Make sure to provide us with a TxId).

Info: X-Cash’s native chain has a block time of 5 minutes, and typically you should expect to wait for 15 minutes (3 confirmations) before the transfer will appear in your deposit address. The 5 minute block time is lengthy, however, our TurboTX feature will make the block time irrelevant.

Once the transfer is complete, you will see your transaction in your Deposit History

Tipping or Sending X-Cash with Privacy.

• Select a Social Media Account Type and choose where you want to send X-Cash to. (Currently, only Twitter is supported.)
• Enter the User Name or Used_ID of the person you’re sending to, or add multiple Receivers.
• Select in full increments the amount you’re sending
• (NOTE: If you have multiple receivers, then each will get the amount specified i.e. If you are sending to 2 people and select 2 XCASH then you will send 4 XCASH in total.

To speed things up you can add your Favorites to your Social Address Book. When you click Select it will prefill the User Name or User ID field above.

Your central control hub

You are able to move X-Cash between your internal accounts. This is done without any fees.

For easier identification pay attention to the arrow as it will indicate how your funds are moving.

Withdraw

Withdrawing your funds from the X-Payment platform is very straightforward.

Paste the destination address and indicate the amount of X-Cash you would like to withdraw.

Make sure to VERIFY the destination address as transactions are irreversible.

If you use multiple addresses then it would be best to utilize the Withdraw Address Book.

The X-Payment Platform

On October 3rd, the platform link will be posted to both X-Cash official and X-Payment bot’s twitter accounts:

• X-Cash Official: https://twitter.com/XCashCrypto
• X-Payment bot: https://twitter.com/XPaymentBot

FAQ

We’ve compiled questions and answers in case you get stuck. If your question is still unanswered, please join us at Discord.

Explore

The explore tab contains all the general statistics regarding the X-Payment platform. You will be able to see how you rank up with the other users among other details on the system.

Call for support or feature request?

We have established communication channels through which you can reach us:

• You can open up a Github ticket on dedicated X-Payment Repo
• Join us over Discord through the invite link, find section X-Payment, and tag @Animus#4608
• Send us a DM on Twitter to the account @XPaymentBot

Animus,

X-Payment Lead

X-Payment on Twitter was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

The old way of depositing to X-Payment

X-Payment users were required when depositing to the X-Payment system to provide an XCA deposit address as well as an appropriate Payment ID. Both details, if correct, allowed us to credit the deposited amount of XCASH to the appropriate Discord username. As you can see below, the length of the payment ID screams for potential errors resulting in XCASH being lost if a single character is misplaced (The same applies for the XCA addresses).

In order to move away from errors, and relax the depositing process for the Discord user, we have therefore integrated support for Integrated public addresses.

What is the integrated address (XCB) on X-CASH?

An integrated address is in its simplicity a normal address bundled with some extra data (the payment id). Standard public addresses (XCA) are made of network bytes, public spend key, public view key, and checksum, while Integrated public address (XCB) adds to the structure as well 64-bit payment ID. It is beyond the scope of this article to dive further into technical details, so if you would like to obtain more information we invite you to check the full documentation on XCASH.

As described, Integrated addresses (XCB) are an amalgamation of a standard XCASH (XCA) address and a short payment id, merged into single string.

They are intended to be used when a recipient (In our case X-Payment system) requires a payment id (a unique identifier for the payer) in order to connect the incoming XCASH with the appropriate Discord Username.

The main two advantages of integrated addresses are:

• The XCB address is self-contained, including a previously mentioned checksum, so it becomes much harder for the Discord User to forget the payment id, usually representing a common cause of trouble.
• The XCB addresses use a short payment id (16 characters as opposed to previously integrated 64 characters), which will always be encrypted on the blockchain. This helps even further by increasing privacy and slightly decreasing blockchain size.

It is trivial for us to go from the integrated address to the standard address plus the long payment id. It is however important to remember that with our integration of integrated addresses, you should not view it as an action to obscure one’s address from the sender (In our case Discord User depositing to the X-Payment system).

The shift to integrated addresses is encouraged due to the above-mentioned reasons, and not many exchanges or other merchants building on XCASH currently support it.

How to register yourself with the integrated address?

Obtaining yourself an integrated address through X-Payment Discord Slash commands is straightforward.

Go to a server which has X-Payment installed, then enter any channel that it has access to. Execute command /account get_integrated, then wait a few seconds so X-Payment can create an integrated address for you. As the process of making an integrated address is complex in the backend, we have assigned rate limit of 1 registration per 10 seconds from server scope.

From this point onward you can use just the XCB address for depositing, without the need to provide an extra deposit id like previously. Information returned should be the newly created XCB integrated address as well as the content of it (XCA address, Short version of unique deposit id).

What happened to my previous XCA address and payment id?

Previous deposit details are still stored in our system and can be used for depositing as well. However, be advised that eventually, we will completely abandon the “old way” of depositing and provide only support for XCB.

Where can I check the new deposit details?

Command to check instructions for depositing has stayed the same /account deposit. What is different is the returned information. See the details below in the picture.

Where can I get assistance?

We have established communication channels through which you can reach us:

• You can open up a Github ticket on dedicated X-Payment Repo
• Join us over Discord through the invite link, find section X-Payment, and tag @Animus#4608
• Send us a DM on Twitter to the account @XPaymentBot

Animus

X-Payment Lead

X-Payment: Support for Integrated address deposits (XCB) was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

X-Payment makes your Discord experience exciting again with the emergence of scalable economies, thus granting server owners passive revenue streams.

Here are the steps you need to take as the owner of the server.

Requirements:

1. You are required to be the owner of the Discord server.
2. X-Payment needs to be in the server and have access to at least one channel: It can be invited by clicking on one of the two available invite links:
    — Invite link with all required permissions integrated for the X-Payment to function optimally 100%
    — Basic invite link that requires you to set-up all permissions by yourself.
3. X-Payment MUST have assigned to its role on Server Manage Channel, Manage Role, View Channels, Send Messages, Manage Message, Read Message History, Use Application Commands, permissions for it and Merchant to function optimally.
4. Create a private channel for you and X-Payment and assign it’s role to the channel, with Role having above permissions. This is a “suggested best practice to keep the management flow of X-Payment separate from other public activities.
5. As a server owner, you are required to have a registered X-Payment account. You can do so by executing the command /account register
6. As an owner, you need to register the server into the X-Payment system with the command /owner register server

How to activate the merchant system?

Once you have successfully registered your Discord Server with the system you can register as well for X-Payment merchant tools by executing command /owner register merchant from within a public channel to where X-Payment has access. Upon successful registration, X-Payment will respond with a notification in the channel where the command was executed.

X-Payment will create a new channel group named X-Payment with channel #merchant. This channel serves as the hub for X-Payment to relay activities such as purchase receipts, perks expiration, etc.

And that’s it! We would like to congratulate you on successfully activating Merchant tools 🥳… We are however not quite finished. In order to receive your first revenue stream, let’s register your first monetized role.

How to monetize Discord Role and make it purchasable for your members?

Create a role in any channel that X-Payment has access to using the syntax below.

Replace the placeholders (e.g. <role_name>) with the appropriate data.

In any channel where you can see X-Payment, create a role using the following command :

/merchant monetize <RoleName> <XCASH amount> <Duration in weeks> <Duration in days> <Duration in hours>

Above is the basic syntax, replace the value between <> with the appropriate data and delete the <>.

This:

/merchant monetize <DOTALegend> <9876> <4> <0> <0>

becomes:

/merchant monetize DOTALegend 9876 4 0 0

Parameter information.

• Decimal values aren’t permitted in X-Payment.
• Duration is the time until the expiry of role purchase.
• Role names must be unique in your server.
• All fields must have a value.
• Duration:
  - At least one duration field must have a value of 1 or greater.
  - If you don’t wish to define a value for the other two fields, please fill them with 0.
  - Infinite duration is unavailable at this time.

<RoleName> : A role name can be maximum 10 characters long with no spaces or special characters.

<XCASH amount>: Price of a role.

<Duration in weeks>: Duration in weeks as a number greater than 0 if others are 0.

<Duration in days>: Duration in days as a number greater than 0 if others are 0.

<Duration in hours>: Duration in hours as a number greater than 0 if others are 0.

Command examples:

A monetized role named Test1 with a duration of 1 week, 3 days, and 0 hours at the value of 100 XCASH will look like this:

/merchant monetize Test1 100 1 3 0

A monetized role named Test2 in duration (expires) of 1 hour at a value of 99 XCASH will look like this:

/merchant monetize Test2 99 0 0 1

After a role has been monetized successfully, you will receive a notification in the channel where you entered the /merchant monetize command. The role is now available to be purchased by your members.

⚠️ Warning ⚠️

• The role name is not allowed to be the same as one of the roles existing already on your server. If you would like to monetize an existing one, please use command /merchant init <@Discord Role> <Amount> <W> <D> <H>
• When deciding the length, of the role, at least one of the duration fields needs to be greater than 0. Infinite duration is at this point not available. The minimum which can be assigned is 1 hour (check examples below).

What will happen if I manually delete monetized role/membership from the Discord Server Dashboard?

Once you delete the role from the Discord Interface (not through the use of the X-Payment command), X-Payment will remove the role from the merchant system, making it unable to be purchased. All users who have purchased membership until their agreed removal time, will be removed from tracking as well, however the role assigned to them on the server will stay.

What will happen if I remove X-Payment Bot from my Discord server completely?

In case you remove the X-Payment bot, all merchant activities will be permanently deleted.

How can members purchase roles/membership over your server?

Members have special commands to operate within your merchant system and participate in your economy. Use the /membership command to display all available commands. The full command map is showcased at the end of this article.

Monetized roles can be purchased using the /membership purchase @RoleName command in one of the public channels where X-Payment is active.

Once a purchase has been made, your server wallet will be credited with the purchase amount of XCASH, and a notification of the purchase will be sent to #merchant channel under the channel section named X-Payment (created automatically when you registered the server into the merchant system).

The server member who purchased the role will receive an inbox notification that includes essential information on the amount of XCASH deducted from their wallet, the time of purchase, and the expiration date.

Merchant command map for the server owner

/owner register merchant: Registers merchant for your server.

/merchant : General entry point to access operations with merchant.

/merchant help: Review all merchant related commands over Discord.

/merchant monetize <roleName> <XCASH Value> <Weeks> <Days> <Hour> : Create and monetize Discord role from scratch.

/merchant init <@DiscordRole> <XCASH Value> <Weeks> <Days> <Hour> : Monetize an existing role on the server.

/merchant balance : Check current balance of your merchant wallet.

/merchant withdraw : Transfer XCASH from the servers merchant wallet to your personal one.

/merchant stats: Review statistics of your merchant system.

/merchant active: Review all active roles on your server available for purchase.

/merchant deactivated: Review all deactivated roles that can not be purchased.

/merchant membership help: Review related commands to the management of memberships.

/merchant membership activate @DiscordRole: Activates the selected role which is already registered in the merchant system.

/merchant membership deactivate @DiscordRole: Deactivates the selected role which is already registered in the merchant system and you would like to prevent users to purchase it.

Membership command map for server members to participate in your economy

/membership: The entry point for server members to participate in the servers economy.

/membership purchase @MonetizedRole: Command to be used when a user would like to purchase one of the available roles on the server.

/membership about: An explanation for server members on what membership is.

/membership available: Review all active monetized roles/memberships to be purchased on the server where this command is executed.

/membership live: Review current active purchased memberships members has.

Where can I get assistance as a server owner or where do I report bugs?

We have established communication channels through which you can reach us:

• You can open up a GITHUB ticket on dedicated X-Payment Repo
• Join us over Discord through the invite link, find section X-Payment, and tag @Animus#4608.

Send us a DM on Twitter to the account @XPaymentBot

Some ideas and suggestions for monetization.

• Monthly membership for users to access the latest aggregated NEWS. You can build a section of channels where various types of news will be relayed and offer it as a monthly subscription. This way users do not need to surf various web pages, and can just review channels on what is going on while drinking coffee. You can even make it specific (sports, tech, blockchain, politics, etc.)
• Live concert membership. If you have access to music artists/DJs, you can organize a live Discord concert where the artist would be streaming music on one channel and users would purchase access to it.
• Online education and training sessions have become quite popular from the start of COVID. You could make education/seminars on a monthly basis in return for membership purchases.
• Discord dating requires a subscription to access a singles chat of verified users.
• Crypto forecasters who wish to give exclusive time-based forecasts to their subscription users.
• Gaming tournaments require a gate-keeping system in order to vet serious participants.

Please let us know about your experience, and how you have been able to utilize and deploy the X-Payment merchant system and create an economy on top of X-CASH.

Animus

X-Payment Lead

Go back to Part 1: Welcome to X-Payment Merchant.

X-Payment: Setting up your Merchant was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

After more than three years of X-Payment, we are excited to announce the largest expansion to date! The Merchant system seamlessly integrates into Discord servers to transform them into bustling economies. — X-Cash team

(Release on 22nd of August 2022)

So what has X-Payment been up to?

From its first iteration, the X-Payment Discord bot’s purpose has been to execute micropayments between Discord users. Throughout the years it has seen multiple upgrades revolving around code base improvements, styling, and expansions of integrated commands, however, less had been done to expand its functionalities to become an integral part of our strategy.

How does that fit into the whole picture?

X-Payment’s team focus has always been on bringing X-Cash to the world over social platforms. As a part of the X-Cash Ecosystem, we strive to develop products that allow our users freedom beyond the expected wallet functions and exchange activity, and now X-Payment is closer to this ideal.

Why is X-Payment different?

Many believe that Crypto bots on social media are unable to do more than send tips, though we believe this is a self-imposed limit. When new features are added to social media Crypto bots they typically are used for a novelty period before the user moves on to never use them again, thus resulting in the above limit misperception.

X-Payment has focused on features that people need and will want to use frequently.

Key features of X-Payment

• X-Payment has the only private/public transaction functions available for social media use right now.
• Simplified for users to begin using right away.
• Transactions are instant and free.
• X-Payment is available on multiple platforms.
• Merchant tools to allow you to build your micro-economy

What are our objectives?

We are the first to offer a comprehensive package that blends the lines between retail consumers and retail operations. In simple terms, our goal for X-Payment is to fully allow anyone safe access to Crypto through the platforms they’re most comfortable with. The Merchant system’s purpose is to enable anyone to manage their own economy, simply, and without bureaucracy, start-up costs, or obligation.

Key terms

Customer: Discord server member.

Retailer: Discord server owner or management staff.

Merchant system: X-Payment’s merchant tools.

Where does the need for a Merchant system arise?

If you use Discord:

• You may come across servers offering VIP access to their secret channels with complicated (and sometimes risky) access protocols.
• Perhaps you are a Retailer with a monetization strategy that is time-consuming to manage.
• Maybe you can’t find trustworthy managers to lighten the workload?
• Or you may have abandoned this ambition entirely due to not having adequate tools.

To better understand the origins of the need, we reviewed the operation of monetized channels and paid particular attention to interactions between Customers and Retailers.

Here is our solution.

Overview

The Merchant system is an expansion to X-Payment built by the X-Cash team.
The Merchant system enables variable duration role assignment to Customers who purchase a role from a Retailer. Subscription roles give Customers access to exclusive channels as defined by the Retailer.

How the Merchant system works

By registering the Discord server in the Merchant system, a new server wallet and an X-Payment channel category are created with a private #merchant channel.

The server wallet is used to receive XCASH from sales (think of it as a “corporate wallet”) and the #merchant channel is used to relay notifications on all purchases (like the bookkeeping).

With the execution of just a few commands, you are able to register in the Merchant system and monetize Discord Roles. You can create as many monetized roles as Discord allows (to our knowledge 250 is the maximum). Once the role is created the only thing that is left to do is to assign the role’s parameters and you are ready.

What happens in the background once a role is purchased?

X-Payment monitors for purchases (and kindly informs you of the purchase), transfers made to the Retailer’s wallet, roles assigned to Customers, calculates the role expiration date, and removes the role from the user once the pre-agreed end date has been reached.
For the Customer, once the purchase is final, the required amount of XCASH set for the monetized role will be automatically deducted from their X-Payment wallet. They will receive a payment slip of purchase with a calculated expiration date, and a purchased role assigned to their discord account.
For both, the Retailer and the Customer, we have a full set of commands which we will introduce in later articles.

Customer

A satisfying Customer experience is key to the Retailer’s success, and self-serve access to exclusive channels after purchase is convenient for the Customer as provided the role is clearly defined, the only limitation is how much time it’ll take the Customer to decide on whether they should make the purchase.

Customer protocol

For the Customer to participate in the server’s economy one needs to transfer the exact amount of cryptocurrency specified by the server’s management staff to the server’s hot wallet address (wallet where they collect payments), to obtain special benefits for a set-time duration.

When the transfer is successfully processed, the Customer is required to send a valid transaction ID to the server’s administrative person as proof. Here the user is faced with another constraint due to the potential delay in the processing time. This is something that is not acceptable, as a Customer should obtain benefits instantly after the transaction is validated.

Customers should be satisfied:

1. Ability to make payment over Discord with one user action and without the need to further verify the purchase with the Discord server staff.
2. Access to purchased membership/role has to be done immediately once payment is processed.

Retailer

The Retailer seeks to allow Customers to have a memorable experience regardless of the Retailer’s monetization strategy. It is the experience that causes repeat custom, and X-Payment’s Merchant System makes this process easy for the Retailer. The Retailer defines the parameters of purchasable Discord Roles and allows the Merchant system to remove the tedious management tasks Retailers are required to execute to successfully manage the Discord server economy.

Retailer protocol

When administration staff receives the verification of the payment for their services, they need to verify the received transaction ID with the incoming transactions to their hot wallet. Once successfully identified, a transaction id with amount, date, Discord username, and expiration date needs to be tracked separately in a spreadsheet-like document to keep everything in order. Once the aforementioned steps are completed, the designated staff is required to give access to the user by assigning him a dedicated role. That however does not represent the endpoint of the retail management process.

Usually, servers offer their members time-limited access of daily, weekly, or monthly lengths.

It is required for them to be extremely careful when handling multiple users who apply at different times and represent different expiration periods. Some of the Discord servers have changed the subscriptions to just a monthly basis and some slots are limited, where payments are collected before the start of a month. This allows them to monitor the subscriptions and manage expiration with ease. By imposing such actions they are losing Customers as someone can not make the due date of payment collection period or monthly time frame does not fit the needs of the Customer. To finish up with the ”Cherry on the top of the messy cake”, the whole management process and monitoring can be further jeopardized due to human error, as once the server grows to over 50+ members, monitoring and processing become time-consuming with a lot of data.

Retail needs to be satisfied:

1. Need to have such a system in place that administration of the server could divert the time from management into content production and quality improvement.
2. Need to have multiple types of roles/memberships to be purchased on the server to open up and expand various income channels.
3. Automated system for instant payment processing.
4. Automated system to handle the management of the Discord Roles upon payment and removal once the time period from purchase expires.
5. Easy tracking of payment histories.

Mutually beneficial relationship between Retailer and Customer

With the possibility of recurring subscription spending and unlimited access for Customers, the Retailer can lower costs for the Customer as the Retailer knows that more value can travel to them over the long term in contrast with a one-time payment with a higher price point.
Discord’s setup combined with X-Payment’s Merchant system allows deeper relationships to form between Retailer and Customer.

Use cases where we deliver a complete solution

Case 1

User A sells artwork via the established platforms, spends a lot of time and resources using self-promotion and paying for multiple platforms’ premium subscriptions to gain exposure, and still has to split sales profits with the platform and payment processors.

Case 2

User B is a musician who is struggling to gain a following using the established platforms, and the YouTube algorithm is giving user B unfavorable treatment. User B can open a Discord server and set the price for a subscription to view content, and remove the prior platform’s restrictions and biases.

Case 3

User C offers trading advice to a private group and wants to remove the complexity of tracking which group members remain eligible to keep receiving advice.

Case 4

User D sells adult content and wants to move to a less saturated platform for a better chance at success while removing third-party commissions.

Case 5

User E gives exclusive live streams to closed groups and wants to make entries exclusive.

Case 6

User F is a Singles chat that requires time-limited speed dating channels, and a need to give users who are serious about dating access to exclusive channels amongst like-minded individuals.

Case 7

User G gives private tuition and wants to keep track of student eligibility.

Case 8

User H is an Indie game developer and wants to run closed testing with members of their community who are supporting the project’s development through subscription.

Case 9

User I has files to share but on the condition that User I is first compensated at least once.

Case 10

User J is a celebrity and wishes to go further to connect with fans. User J also wants to keep abusive messages outside of their space. Using X-Payment’s Merchant system inside Discord enables User J to set an entry price which will force the abusive message senders to reconsider the costs of sending abuse.

How about the fee for using such a service through X-Payment?

As it has been till now, services and use of X-Payment functionalities, for the time being, are completely free of charge.

Where can I find support?

We have established communication channels through which you can reach us:

• You can open up a GITHUB ticket at the X-Payment Repo.
• Join us at Discord and tag @Animus.
• Send us a message on Twitter to the account @XPaymentBot

We wish you success through X-Payment! Be sure to let us know about your experience and the economy you are leading. Let’s do something together ;).

Animus,

X-Payment developer

Continue to Part 2: Setting up your Merchant.

Welcome to X-Payment Merchant was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

Hello Community,

2022 is a year of immense changes in the world, and though some unfortunately have a sense of dread about the future, a few see an undeniable flame of hope. The hope radiates and gives clarity to what the shadows conceal thus allowing the eyes to see. What is under the shadows is for those who witness the flames’ radiance.

Before this article gets buried by our heavy release schedule, thanks. Thanks for being an early supporter and witness to X-Cash’s maturation– though we are still at the beginning and have a ton of untapped potential to realize. Our new website release is a starting pistol for many more exciting product releases, expansions, and events over the coming months as we take a leap beyond the Web3 to make Crypto safe and rewarding for all: the X-Cash way.

A few cosmetic changes

On July 25th, clear your cookies or enter xcash.foundation via private browsing (or a different browser), as upon entry you will be greeted with a completely new design. Things have gotten dark, though our familiar colors still remain. Our orange (#FA741C) is boosted against our dark gray (#1F1F1F) background so that all of our new arrivals can become familiar with our signature orange immediately.

You will also notice the adoption of a single-page design, which contrasts with our prior multi-page site. We still use pages, as is evident from the navigation bar directly above, though this time around, for the majority of your journey, you’ll only have one page to load which will give you a more immersive experience. All pages are now sections and are navigable using scroll, or appending /#section-title to the URL e.g to enter directly to the metrics section: https://xcash.foundation/#metrics.

Following you vertically on the right of the landing page is a wallet widget that lets you navigate to our wallet download page. This is useful if you get the strong urge to download a wallet mid-section. On the left side of the landing page you’ll see an autonomous (semi-ominous) orb. Be wary of the orb.

An evolving process

This is a living breathing project that will be updated when new elements have a need to be added, such as new features, partnerships, and exchange sections– all flames need oxygen! You will notice talk of refactoring which will take place between autumn/ fall of this year through Q2 of 2023. The site as you’re seeing now is currently in a transition from old to new, and due to its living breathing characteristic, is continuously evolving.

Please, via GitHub continue telling us what features you wish to be added, and bugs that you may encounter. Remember that this is your website and that we are improving & delivering through your suggestion & participation! Thanks to the community for assisting with testing, creating content, and giving feedback. And special thanks to !executor!, mryoso1994, Animus, Zurg, and our XCadians!

We will still be building years from now no matter the circumstance, so let’s grow our flame’s radius so more people have a brighter tomorrow!

Thank you.

X-Cash Website Update was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

Dear Community, we are taking the time to write today, to give a first half of the year review and a look ahead to the second half of the year.

In the first half of the year there was a lot of internal stuff to do. The team restructuring was started and completed. You will be able to see the team members and their roles once we release the new website.

There was a lot of coding to be worked on, and unfortunately their were no new releases, but most projects that the team were working on are about 80%+ done at this time.

There also was the process of restructuring some of the servers. This is still a work in progress.

Second Half of the Year

The second half of the year should be much more exciting as the work we have done in the first half of the year will be ready to be released. Starting in July, you will see X-Cash take on a new release schedule that has not been done in the coin’s history. Traditionally, we have always had a few projects being worked on by different team members at the same time and have had releases every quarter or two, due to the nature of the projects. This will change in this second half of the year as we have a larger team, working on more projects. The timing worked out to where most people are finishing around the same time. Because of these two factors we can now for this second half of the year transition to a more stable and timed release schedule.

We don’t want to list each release here today or what the frequency of the release schedule will be, but all categories of xcash have been worked on, and will be improved in this second half of the year, including:

X-Cash blockchain
X-Cash second layer protocols
X-Cash tools and building tools
X-Cash products (X-Bank, X-Payments, etc etc)
Existing X-Cash services

The testnet will be revamped with a new protocol test this year (hopefully two new protocols), extra X-Cash DPOPS functions, and a new reward structure as well.

Of course, we are still working on marketing and exchanges as well. In the first half of the year there was a few marketing efforts, including this yahoo news article about our project.

https://www.yahoo.com/now/x-cash-innovative-privacy-centered-124000661.html

We also worked on exchanges as well. We really want to find one that will work for the community and be one that the community will want to use, so it will take extra time as we go one or two at a time, talking with the exchanges, the team, and the Paris founders about, etc etc. This is a weekly thing were working on.

Once again, I want to thank everyone who continually supports this project.

We will be releasing an article about each new release or piece of information, so make sure to stay up to date every week, to not miss a release.

First Half Recap, Second Half Look Ahead was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.

Dear Community,
Today we are releasing xcash-core 2.2.0 and xcash-dpops 1.2.0

Note: You will need to update before block height 910000 which is expected to happen around Wednesday, March 23, 2022 03:00:00 UTC

XCASH-CORE Update 2.2.0

Some highlights of this update:
- Updated hashes so xcashd can sync, before we fixed the issue.
- xcashd syncing improvements at block 910000
- Removed most mining code. Test show virus false positives dropped as well.
- Fixed the docker file
- Boost 1.77.0 compatibly
- GCC 11 compatibility
- Fixed debug build not working

You can read the full list, and how to install at https://github.com/X-CASH-official/xcash-core/releases/tag/2.2.0

XCASH-DPOPS Update 1.2.0

Some highlights of this update (and the 1.1.0 update):
- Fixed synchronize-database-from-network-data-node parameter
- Added delegate error reporting parameter
- Added limits to shared delegates API for pagination
- Fixed syncing stability at time 1648221480 (Friday, March 25, 2022 15:18:00 UTC)
- Fixed autoinstaller custom paths
- Fixed autoinstaller search strings for finding install locations to make them more robust

Instructions on how to update xcash-dpops is at https://discord.com/channels/470575102203920395/746277791556698182/952931355401015376

Thank you everyone.

XCASH Core and DPOPS Update was originally published in X-Cash on Medium, where people are continuing the conversation by highlighting and responding to this story.