All-in-one online bookkeeping and tax solution

xendoo

The artificial intelligence of the chatbots is revolutionizing the customer experience. They can provide useful information to customers when they need it. Hence, a number of companies that use AI Chatbots have grown exponentially. It provides them with proactive assistance to their customers. Many brands have supercharged their customer service experience with chatbots. It has grown and improved to capitalize on various social networks and messaging platforms. As per the stats, nearly 80% of businesses will have their own Chatbot by 2020 end. It has surpassed usage from 30,000 in 2016 to approx. 100,000 nowadays. Hence, chatbots can now be considered as the new-gen tech. Facebook’s Messenger In this blog, we will look at the various AI Chatbot Platforms that would surely boost up your business revenue. Hiring developers from top chatbot development companies can also benefit you in the long run. Check out the list below: 1) Chatfuel It creates smart and intelligent AI chatbots and allows you to automatically provide answers to frequently asked questions from your customers or prospects, such as in Facebook Messenger. You can even transfer the conversation to a human agent in case your bot cannot answer the question properly. This automation ensures that you never miss a chat from your customers and can continue to provide the assistance they need. Related Blog: How Blockchain & AI Integration is Changing Business Landscape? 2) Meya.AI It has a code editor, live debugger and a visualizer. With the help of Meya, companies can take for their customer service. It helps companies create bots that help their customers in messaging and customer support applications. You can build, train and host your robots in Meya. And you can also easily scale your bots. Meya easily integrates with third-party applications, which increases its ease of use. advantage of AI 3) Imperson This platform develops business AI chatbots that support video, text, audio, AR and VR in the main messaging platforms. Their conversation robots provide authentic and engaging chat experiences for clients. The conversation browser uses the memory of relationships, the attempts of NLP users and the context of a deep dialogue to direct the conversations. And the moderator of artificial intelligence helps to reach the objectives of the clients. Imperson provides an end-to-end bot solution by hosting and deploying your bot and providing information in real time to improve its performance. 4) Flow XO Without having to learn any code, it allows you creating smart chatbots. With its simple drag-and-drop editor, you can create logical workflows and then connect your AI chatbot to the platform you choose. FlowXO integrates with a large number of third-party applications. You can create bots that integrate with services like Salesforce, Google Sheets, Twitter and more. Its hosting and administration features make it one of the best AI chatbot platforms. Read More: Chatbots can make technology more accessible 5) Xenioo Best Part: Free registration Without any line coding, you can build amazing chatbots using this easy-to-use platform. It allows you to instantly build and launch intelligent chat chats for your website or any social networking platforms. You can use it for multiple channels, including Slack, Amazon, Facebook, WhatsApp, Telegram, and many more. In addition, these AI chatbots are able to understand and respond to complex and multilingual expressions with the help of the NLP engine integrated into the platform. It even has a training module that allows you to train chat chats by creating intentions and expressions. Read Blog: Top Chatbot Development Companies For SME's and Startups 6) Botsify It helps you create smart AI chatbots for your website or slack without having to spend your time and efforts on coding. Botsify offers multiple add-ons to help you integrate it with your Shopify store, RSS feed, Google Sheets, or Google search. It has an easy-to-use drag-and-drop UI and is powered by artificial intelligence and machine learning. This allows machine learning developers to seamlessly transfer the conversation from a bot to a human agent in situations where the bot is not properly equipped to assist the client. Theplatform also presents conversation forms through which you can collectinformation about your potential customers through chatbot conversations. 7) MobileMonkey You can use it to manage a series of lead generation activities, such as chat streams, drip campaigns, and list creation. It also allows you to automate customer service by providing answers to frequently asked questions and reduces waiting time. You can even cancel your AI chatbot and jump into the conversation at any time, without problems. It helps you build chatbots which can take your Facebook Messenger marketing to the next level. 8) Aivo It is one of the best AI chatbot platforms as it enhances customer support experience and helps organizations respond in real time through text or voice. It can help you increase conversions and optimize your resources. Aivo’s AgentBot can be easily integrated with third-party platforms such as Zapier, Live, Zendesk, Salesforce and many others. It adapts to the rules of a channel and responds automatically to provide its customers with a personalized experience. 9) Pandorabots Pandorabots provides solutions for the complete development of turnkey chatbot. This platform is one of the oldest and largest AI chatbot hosting services in the world. It allows bidirectional communication to scale. You can create and implement chatbots on your website, mobile applications and popular messaging platforms such as Line, KiK, Twitter, Telegram, and Slack. Pandorabots implements and supports AIML open standards. 10) ManyChat For marketing, sales and support systems, it helps you easily create Facebook Messenger chatbots. Its visual creator of drag-and-drop bots helps you set up a Facebook Messenger bot in no time. It helps you transmit your messages effectively. You can also automate your Messenger marketing and send messages based on delays or certain user actions. It also provides you with a set of tools to help you increase your Messenger audience. 11) Boost.ai It can help companies to build conversational chatbots. This can help you provide faster support to your customers and automatically reduce your waiting time by providing answers to frequently asked questions. It has an easy-to-use API along with a conversation flow editor that helps you easily train your AI chatbot without requiring any technical knowledge. Boost has been successfully tapped by leading companies in domains viz. human resources, telecommunications, banking, insurance, and even in the public sector. Hence, it is one of the best AI chatbot creation platforms. Final Note: So far we have seen some major AI chatbot platforms that let to enhance their customer experience. You can even broadcast your special offers and other messages easily using these chatbots. Ultimately, these will help you provide efficient and quick customer support. companies build smart and intelligent chatbots However, we have listed our best AI chatbot platforms for the businesses in 2019–20. : I work at , a company that creates Chatbot Solutions Disclosure Value Coders

Eleven Trending AI Chatbot Platforms

The privacy coin project Horizen team once claimed: "If Satoshi Nakamoto wants to design a sidechain for Bitcoin, then he should design something analogous to Zendoo." Zendoo here is the sidechain protocol designed by the Horizen team. Let's study the Zendoo protocol white paper today. The Zendoo white paper was jointly written by the Horizen team and the IOHK team. The protocol supports a sidechain of any type, including the sidechain of the UTXO model, the sidechain of smart contracts, and even an ordinary centralized application. It is understandable that the Zendoo protocol only supports cross-chain funds because Horizen is a UTXO-model private currency public chain that does not support smart contracts, hence the cross-chain agreement is only cross-chain funds. Zendoo utilizes zero-knowledge proofs to support a decentralized approach to achieve cross-chain purposes. The Cross-Chain Mode There are four cross-chain modes in total: Let's further study: FT (Forward Transfer) FT operates on the main blockchain: it transfers the assets on the main blockchain to the sidechains. The protocol is also quite simple: the main blockchain treats FT as a special transaction, destroying coins on the main blockchain and providing metadata concerning the payment on the sidechains. The side chain needs to monitor the main blockchain in real-time. If the latest block of the main chain does not contain FT transactions, the side chain will only use the hash of the block in the main blockchain as a reference and add it to the side chain; if the latest block of the main blockchain contains FT transactions, the entire block header, all FT transactions, and the Merkle path of all FT transactions will be introduced into the side chain as a reference. In this way, anyone on the side chain is able to verify whether the transaction is legal instead of going to the main blockchain for query verification. BT（Backward Transfer） BT operates on the side chain and transfers the assets on the side chain to the main blockchain. As mentioned before, IOHK is also one of the authors of the Zendoo white paper, so we can see the resemblance of the Ouroboros protocol in the design of BT. Like the Ouroboros protocol, the protocol design of BT also involves the concepts of epoch and slot, as shown in the figure above. A withdrawal epoch is composed of lens and slots, and the len has different parameters for different side chains. If a withdrawal certificate is not submitted to the main chain within this period of time, the side chain will be considered as ceased (for instance, a withdrawal certificate in epoch is not submitted to the main blockchain in the first len blocks in epoch +1), and subsequent withdrawal certificates will not be accepted by the main blockchain, but the funds of the side chain can still be withdrawn. The B in the above figure is a slot. The side chain forger (block producer) will package the slot with BT signature and submit the withdrawal application certificate to the main blockchain within the specified epoch time. Regarding the withdrawal certificate, we will talk about it later. i i The main blockchain does not care about the role of submitting the withdrawal certificate, and the way the withdrawal certificate should be packaged is a consideration for the side chain but not for the main blockchain. BT = (receiverAddr, amount) Among them： receiverAddr-the address of the recipient on the main blockchain amount - transfer amount A Withdrawal Certificate (WCert, Withdrawal Certificate) is a standardized posting that allows the side chain to communicate with the main blockchain. This requires at least 51% of the block producer signatures to prevent fraud, and then send it to the main blockchain. The main functions are: Send BT to the main blockchain As a heartbeat message, the main blockchain can identify the state of the side chain It is defined as below: WCert = (ledgerId, epochId, quality, BTList, proofdata, proof) Among them: ledgerId-sidechain id to create WCert epochld-the id of a withdrawal epoch, generally increasing in order quality-indicates the quality of this withdrawal certificate (actually, it is the block height of the last status update) BTList-an array of multiple withdrawal transactions within a withdrawal period Proofdata-public input parameters used by SNARK verifiers Proof-the proof used by the SNARK verifier The main blockchain contains vk (written when the sidechain is registered), and the certificate generator of the sidechain (can be anyone) contains pk. true/false <- verify (vk, public_input, proof) public_input = (wcert_sysdata, MH (proofdata)) wcert_sysdata = (quality, MH(BTList), H(Bi-1), H(Bi)) proofdata = (H(SB_last), H(state_SB_last [MST]), mst_delta) Among them: Bi-1-the last block hash of i-1 withdrawal epoch in the main blockchain Bi-the last block hash of i withdrawal epoch in the main blockchain H(SB_last)-the last block hash of the i withdrawal epoch sidechain H(state_SB_last[MST])-the Merkle hash after updating the state SB_last mst_delta - bit vector modified by MST. Since MST is a fixed-size tree, mst_delta is also a fixed-size bit vector, and each bit represents a leaf of the tree. This is applied for data visibility. In the UTXO model, withdrawal data can be restored on the main blockchain without the need for sidechain data. Bit vector algorithm As demonstrated in the above figure, an MST is in a depth of 3 leaves and with a node of 2³. The grey leaf node indicates that there is an update, and the white leaf node indicates that there is no update. The bit vector algorithm is used to represent the change of MST, which is: mst_delta = (10111001)` The algorithm can effectively in the Data Availability characteristic expansion scheme, that is, , and the root hash after the MST change can verify the legality of the data. For L1 verifiers, it is not necessary to verify all the data but just the changed state. save the data on the chain every time only the transmission of the changed delta value, the root hash before the MST change Surely, if there are large volumes of data and the MST has a lot of leaves, then the bit vector will also be large and will consume a lot of gas. This is the direction that needs to be optimized in the future. 2. BTR（Backward Transfer Request） It is possible that users cannot perform BT operations on the sidechain. For example, the RPC address on the sidechain refuses to access. At this time, if one wants to retrieve the funds on the sidechain to the main blockchain, one can only initiate a BTR operation on the main blockchain. BTR will not directly transfer funds on the main chain, but synchronize this BTR to the sidechain, and go through the process analogous to BT (excluding the user's active part) on the sidechain. BTR = (ledgerId, receiver, amount, nullifier, proofdata, proof) Among them: ledgerId -sidechain id receiver -the recipient on the main blockchain amount - transfer amount nullifier -the unique identifier of this claimed coin (similar to the nonce in Ethereum, anti-double spending) proofdata - publicly entered parameters, which will be discussed in detail later proof -proof of zero-knowledge proof The vk and pk in a ZKSnark protocol are public, so anyone can employ vk to verify the correctness of the proof. true/false <- verify(vk, public_input, proof) public_input = (btr_sysdata, MH(proofdata)) btr_sysdata = (H(Bw), nullifier, receiver, amount) Among them: Others are the same as the above-mentioned WCert, H(Bw) is the block hash of the main blockchain when this sidechain submits the last withdrawal certificate. 3. CSW（Cessed Sidechain Withdrawal） When the sidechain does not respond, for example, the sidechain is attacked or the heartbeat message is not sent to the main blockchain within the specified time. At this time, the funds on the sidechain need to be withdrawn from the main blockchain. It is defined as follows: CSW = (ledgerId, receiver, amount, nullifier, proofdata, proof) The meaning of the parameters is the same as that of BTR. Unlike BTR, CSW will not go to the sidechain to follow the BT process (because the sidechain has no response at the time), but directly complete the transfer on the main blockchain. Detailed Design Withdrawal Safeguard Set a global variable on the main blockchain, increase the corresponding transfer amount when performing FT, decrease the corresponding amount when performing BT, and when withdrawing, the amount cannot be greater than this amount. (This function is easier to implement in smart contracts.) Main Blockchain Refers to Sidechain In order to synchronize the main blockchain and the sidechain, an extra field is included in the block header of the main blockchain to commit all operations related to the sidechain in the main chain block (except CSW, used when the sidechain is ceased). Introducing is to include the root hash of the Merkle tree that is related to all transactions or output concerning the sidechain. scTxsCommitment (Sidechain Transactions Commitment) For example: type MCBlockHeader { prevBlock: BlockId, height: int, … scTxsCommitment: Hash, } Sidechain Refers to Main Blockchain The sidechain (SC) block contains the high reference (or hash) of the main chain (MC), which has two advantages: The sidechain can be synchronized quickly The main chain is forked, and the sidechain can be referenced as a rollback point based on the final height of the main chain As can be seen from the above figure, the main chain block may contain sidechain-related transactions, and the transactions will also be included in the sidechain block, which will also reference the main chain block. Among them, the sidechain contains a reference to the main chain: type MCBlockRefrence { header: MCBlockHeader, mproof: Option [MerkleProof], proofOfNoData: Option [MerkleProof], forwardTransfers: Option [FTTx], btRequests: Option [BTRTx], wcert: Option [WCert], } header- the header that refers to a certain MC block mproof-optional, if the MC block contains at least one transaction related to this SC, this field is used for the Merkle root of the SC, otherwise, it is empty. proofOFNoData-optional forwardTransfers-MC cross-chain to SC btRequests -Request to redeem funds from SC to MC WCert-withdrawal certificate Proof Combination Composing SNARKs recursively can transfer multiple states and finally generate a proof. The transfer (BT/BTR) form of a single token is fixed, so the basic circuit is universal. For example,  ERC20 is implemented in the form of "transfer". Then, base_proof can be aggregated to finally generate a proof. This form of aggregation is actually MMR (Merkle Mountain Range). Then the MMR will be discussed in detail as below. Merkle Mountain Range (MMR) For the aggregation proof of the ordinary Merkle Tree structure, if one wants to aggregate the proofs of 10 transactions into one proof, one needs to aggregate the leaf nodes in pairs. If the proofs of some of the leaf nodes are not yet ready (for example, we set that 10 transactions can generate a base_proof in the ZK Rollup. At this time, 8 transactions may be ready, but the remaining two have not yet occurred), the entire prove process will wait until the leaf node's proof is ready, and then make the aggregation in pairs, and finally aggregate sequentially to generate a merge_proof. MMR has improved the Merkle tree structure. It can first aggregate the generated base_proofs in pairs to generate merge_proof, and then aggregate merge_proofs in pairs to generate merge_proof. As shown in the figure above, when the transactions Tx9 and Tx10 are not yet ready, the base_proofs of the previous 8 transactions can be aggregated to generate the merge_proof (1->8), and after Tx9 and Tx10 are completed, combine this two base_proof to generate a merge_proof (9->10), and then aggregates the proof with the ready merge_proof (1->8) to generate the final merge_proof (1->10). Compared with the aggregation proof of the Merkle tree, MMR has the following characteristics: The efficiency of generating aggregated proofs is high, and the proof time is greatly reduced The structure is more flexible, and base_proof and merge_proof can be aggregated Certificate Submission When submitting, only the node maintainer (Forger/Slot leader) is eligible to be rewarded after submission, and within a specific submission period. If the submission fails or is not submitted within the time limit, it will be postponed to the next competitor. (Slot leader election uses the smallest block hash of an epoch on the main chain to generate random numbers.) In Latus, both the block producer and the prover are rewarded, and the block producer packs, while the prover generates a certificate. For basic state transitions, prove and verify are: proof^{Base}{a} = Prove(pk^{Base}{a}, (s_i, s_{i+1}), (tx_a)) true/false = Verify(vk^{Base}{a}, (s_i, s{i+1}), proof^{Base}{a}) Among them: a ∈ {pay, FT, BT, BTR} {i+1} are public inputs, si= Hash(State_i), that is, public input is the hash before and after the state transition, for Latus, it is the merkle tree root hash s_i，s For the merged SNARK, prove and verify are: proof^{Merge} = Prove(pk^{Merge}, (s_i, s_{i+k}), (s_{i+j}, proof^b_1, proof^c_2)) true/false = Verify(vk^{Merge}, (s_i, s_{i+k}), proof^{Merge}) Among them: b,c ∈ {Base, Merge} proof^b_1 proves that there is such a transaction, tx_1, …, tx_j, enables State_{i+j} = update ([tx_i, …, tx_j], State_i) proof^c_2 proves that there is such a transaction, tx_{j+1}, …, tx_k, enables State_{i+k} = update([tx_{j+1}, …, tx_k], State_{i+j}) Summary Judging from the white paper, Zendoo and ZK Rollup are quite similar. For Data Availability, the former involves the cross-chain generation of proofs, and sidechain transfers cannot generate. The latter will generate proofs for all L2 transactions and submit them to L1 verification. For withdrawal, Zendoo has BT/BTR/CSW, and ZK Rollup has similar operations such as Withdraw/Exit/Force_exit. For MST data maintenance, the existing ZK Rollup implementation basically applies a single node or a centralized node, while the Zendoo node is decentralized storage. Compared with the current popular Polygon, Zendoo is decentralized in the cross-chain form, and anyone can submit a ZK proof, while Polygon applies authorized multi-signature bridges to control the billing on both sides of the contract to achieve cross-chain. As for the withdrawal time, Zendoo needs to generate a proof and submit it to the chain, the process which is more time-consuming, while Polygon is more centralized and time-controllable. Regarding the difficulty of implementation, Zendoo also needs a prover for generating proof in addition to the node. This requires the realization of a zero-knowledge proof circuit, which is more difficult to develop, while Polygon only needs to implement multi-signature contract control. Reference https://heap.horizen.io/ https://www.horizen.io/assets/files/Horizen-Sidechain-Zendoo-A_zk-SNARK-Verifiable-Cross-Chain-Transfer-Protocol.pdf https://www.horizen.io/assets/files/whitepaper-snarks.pdf https://academy.horizen.io/horizen/expert/sidechains/

Zendoo Protocol: A Deep Dive

ZenIP 42207: The Turning Point in Horizen's Privacy Token Strategy The recent development in the Horizen ecosystem, particularly ZenIP 42207, marks a significant shift in the network's approach to privacy tokens. ZenIP 42207, proposed on January 4th, 2024, aimed for the complete removal of the shielded pool from the Horizen mainchain. This initiative follows the earlier ZenIP-42204, which began the deprecation of shielded pool access. The move is a response to the changing regulatory landscape around privacy tokens and symbolizes a strategic shift from privacy-centric features. Key Changes and Implications : All functionalities related to shielded transactions, including z-addresses, will be entirely deactivated. This prevents any transaction involving the shielded pool. Disabling of Shielded Transactions : RPC calls like z_sendmany and z_mergetoaddress, specific to shielded transactions, will be deprecated. RPC Calls Removal : Users will receive necessary tools and guides to transfer their assets from the shielded pool before the hard fork. Community support and comprehensive documentation will facilitate this transition. Migration Path for Users : The deactivation will occur via a network upgrade at a specified block height, backed by extensive testing and community preparation. Network Upgrade : Regular updates and guidance will be provided to the community throughout the transition process. Communication and Timeline : ZEN 5.0.0 is slated for release in January and activation in February 2024. Post-activation, shielded transactions, including de-shielding of coins, will not be possible. Important Notice Voting Process and Results : Voting started on January 8th and concluded on January 11th, 2024. Timeline : The Horizen DAO voting used Snapshot and Discourse for governance. Method : The proposal passed with 99.97% votes in favor. Results : The high participation level reflects the community's involvement in Horizen's decision-making process. Community Engagement Next Steps for Users : It's crucial for users with funds in private addresses to transfer them to transparent addresses using Sphere by Horizen or zen-cli before February 2024. Unshielding Funds : Directly unshielding funds to exchange deposit addresses is discouraged. Caution Against Exchange Deposits : Failing to transfer ZEN from shielded pools before the hard fork will result in a loss of assets. Risk of Loss Comparative Analysis Feature/Aspect Pre-ZenIP 42207 Post-ZenIP 42207 Transaction Privacy High (shielded pools) Limited (transparent transactions only) Regulatory Compliance Lower (due to privacy focus) Higher (aligns with evolving regulations) User Experience Complex (due to shielded transactions) Simplified (transparent transactions only) Community Involvement Limited (less governance engagement) Increased (active participation in decision-making) Network Security High (with shielded transactions) Maintained (through transparent ledger) The approval of ZenIP 42207 is a landmark moment in the Horizen ecosystem, demonstrating a proactive response to regulatory changes and a shift in strategic focus away from privacy-centric features. This change, while controversial to some, ensures the network's longevity and compliance with emerging regulations, but also highlights the importance of community involvement and transparent communication in the governance of blockchain projects. The Backbone -Large and Most Decentralized Node Infrastructure One of Horizen's standout features is its massive node network, setting an industry standard for security and decentralization. Employing a multi-tiered node system, each node plays a pivotal role in supporting the network and is duly compensated for its contribution. This unique structure not only reinforces the security of the ecosystem but it also ensures a level of decentralization that is unparalleled in the blockchain space. ZenNode - Democratizing Passive Income Opportunities commitment to inclusivity and accessibility can be seen in its ZenNode program. Designed to empower anyone, regardless of technical proficiency, to run a ZenNode and earn passive income, the program stands as a testament to the platform's democratizing ethos. Whether you are a seasoned tech enthusiast or a novice, hosting nodes through vetted third-party providers offers a quick and straightforward entry point to begin earning node rewards. Horizen's The process is streamlined into three simple steps, emphasizing the platform's user-friendly approach. The Total Active Horizen Nodes dashboard provides real-time visibility into the thriving node network, allowing participants to gauge the network's robustness. Not only this, to further enhance transparency, Horizen provides an Earnings Calculator, enabling users to estimate their potential rewards. ZEN, the Native Cryptocurrency for the Horizen Ecosystem At the heart of the Horizen ecosystem is ZEN, its native cryptocurrency. ZEN introduces an optional privacy feature that puts users in control of their digital footprint. This innovative approach aligns with Horizen's commitment to adaptability and user empowerment in an era where privacy concerns loom large. A Strategic Shift - Responding to Regulatory Dynamics Horizen's recent decision, exemplified by ZenIP 42207, marks a strategic pivot away from privacy-focused features. The proposal, which garnered an overwhelming 99.97% vote share "for," underscores the platform's responsiveness to the evolving regulatory environment around privacy tokens. The complete removal of the shielded pool from the Horizen mainchain is a bold step, reinforcing the project's commitment to compliance and strategic alignment with regulatory shifts. Looking Ahead - Dynamic Future for Horizen As Horizen gears up for the release of ZEN 5.0.0 in January, followed by its deployment on Mainnet in February 2024, the platform continues to shape the future of blockchain technology. The comprehensive removal of the shielded pool, coupled with the continued growth of the node network and advancements in sidechain technology, positions Horizen as a frontrunner in the rapidly evolving blockchain ecosystem. In the spirit of community engagement, the successful voting process for ZenIP 42207 underscores Horizen's commitment to democratic decision-making. As the platform evolves, it invites users to actively participate in discussions on Discord, Discourse, and Twitter, fostering a collaborative environment where the community's voice plays a pivotal role in shaping the platform's trajectory. In conclusion, Horizen's multifaceted approach, spanning from its unparalleled node network to innovative sidechain technology and strategic decision-making, paints a picture of a platform poised for dynamic growth. Whether you are an enthusiast looking to earn passive income through ZenNode participation or you are a developer seeking a scalable and private blockchain solution with Zendoo, Horizen offers a comprehensive ecosystem that adapts to the evolving needs of the blockchain landscape. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our brand-as-author program. Be it through direct compensation, media partnerships, or networking, the author has a vested interest in the company/ies mentioned in this story. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR

XENDOO

xendoo.com

-- employees

Since n.d.

COMPANY RANKING

XENDOO

EVERGREEN INDEX #11465

Representing this company? Click here to claim and customize this page!

xendoo WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

XENDOO

xendoo.com

-- employees

Since n.d.

COMPANY RANKING

XENDOO

EVERGREEN INDEX #11465

RELATED COMPANIESRANK

STORIES ABOUT XENDOO

Representing this company? Click here to claim and customize this page!

xendoo WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!