OST.com/OST-Platform

pyramus

@pyramus

yeah sure. I would recommend to walk through some more of the Node examples, because there seems to be a lot of syntax errors as well (as me and @schlinkmumpitz mentioned). I really love the amount of examples you provided but it's a missed opportunity when they don't run ;-)

Ankit Yadav

@ankit-yadv

Hi @nguyenpc,

You can create a ticket here https://help.ost.com/support/home

Daniel Pham

@nguyenpc

Hi @nguyenpc,
You can create a ticket here https://help.ost.com/support/home

I've submitted a ticket, thanks.

Shinto2000

@Shinto2000_twitter

@pyramus Yes, my tx's were company-to-user, i had to make sure you get the correct rules address in first (to
Required Rule address. You can get the rule address by using list all rules API.)

i got the same error until i got the Rules address from 'Direct Transfer', and placed into the (to)

let executeParams = {
user_id: "9931e53a-83e6-4f9c-92c2-1e4319eab349",
to: "0xe2c560d01f28d2962c934c747234f1453170fae8",
raw_calldata: raw_calldata,
//meta_property: meta_property
};

Ankit Yadav

@ankit-yadv

Thanks @Shinto2000_twitter for mentioning rules address, the to address is the address of rule that you want to execute.

@pyramus you can also follow this execute transaction guide, it shows a step by step process to execute transactions.

https://dev.ost.com/platform/docs/guides/execute_transaction/

@pyramus let us know if the above solves your error.

pyramus

@pyramus

Well I doubt anybody here actually read my intial issue. It's about adding meta_property details, which nobody is capable of doing.

@ankit-yadv @Shinto2000_twitter please show me an actual example where you've been able to attach meta_property details with a transfer in node

@ankit-yadv no. this is not node.

@Shinto2000_twitter yeah already know that. As said before,

let meta_property = { "name": "Signup Bonus", "type": "company_to_user", "details": "Credit to get started." }; executeParams = { user_id: companyUserId, to: contractRuleAddress, raw_calldata: raw_calldata, // meta_property: meta_property };
executes correctly / but crashes when I uncomment meta_property line
this is exactly like the API specs, but please try to run your own examples from Node.js and you'll see it will fail

Ankit Yadav

@ankit-yadv

Hi @pyramus,

I have updated the sample code for node.js. They are working with meta_property included.
https://dev.ost.com/platform/docs/api/?javascript#execute-a-transaction

The only constraint with meta_property is, it should have value for all three attributes. None of the attributes can be empty. meta_property as a parameter is optional.

Shinto2000

@Shinto2000_twitter

Hello team, wanted to see if there was a way to 'automating' the process of (inputing in the user email address in the admin wallet page). Is there a way you guys could share what the front/backend call looks like? (use case - we have a test economy, but i have to manually enter in each user's email address, would prefer we have a webpage where individual users can input in and receive a download wallet app email)

pyramus

@pyramus

Thanks for the fix @ankit-yadv, the code now works.
Perhaps you should also update the API documentation and mention that meta_property is actually NOT required, but in case it is used the child attributes ARE indeed all required and cannot be empty?
alt

pyramus

@pyramus

@ankit-yadv I also found something else: using the full stop "." character inside the string child attribute details is not allowed and will break the request. Might be handy to mention, because currently only a max length is specified as limitation to this specific child attribute in the API documentation.
alt

pyramus

@pyramus

Last but not least: please notice that ^ is not the exponentation operator, but the XOR operator in Javascript. So this (uncommented) part in the Node.js example won't work as expected. You should use Math.pow (or ** more recently) instead.
alt

Ankit Yadav

@ankit-yadv

Thanks for your inputs @pyramus. We will be reflecting changes soon.

ldumaine

@ldumaine

Hello! Is this the right place for feedback about the wallet application?

When you initialize the wallet you have to chose a pin code..

(I'm referring to the android app BTW)

ldumaine

@ldumaine

And you have to validate your input by using "enter" on the keyboard.. This isn't that obvious at least for me.. It would be nice to have an indication and/or a GUI element like a button..

Nother thing the wallet doesn't prevent the user from sending a "zero" amount.

Ankit Yadav

@ankit-yadv

Hi @ldumaine, yes this is the right place to give us feedback about the wallet application and OST Platform. I appreciate your inputs, we will be improving upon these inputs in our next release.

That would be a minor release though to improve the experience at earliest.

Mario Jefferson

@Orami

i have an acct i need verified for the demo acct

Ankit Yadav

@ankit-yadv

@Orami, can you explain more?

Shinto2000

@Shinto2000_twitter

On testnet, when we put in a meta_property "details", i'm looking at the tx on the block explorer but dont see the text from details. Is it supported or am i reading it incorrectly?

Kevin FS

@kevinfs510_twitter

@Shinto2000_twitter Re 'automating' the process of inputting email addresses: Multiple email addresses can be entered at once, separated by a comma

@Shinto2000_twitter Can you share link to tx please?

Shinto2000

@Shinto2000_twitter

https://view.ost.com/testnet/transaction/tx-1406-0xb89b291e3a0cb076c97b326ca91429b4dc1fee14ed93779263fab4622c88b8a8

Here's my properties

meta_property = {
"name": "download" , //like, download
"type": "company_to_user", // user_to_user, company_to_user, user_to_company
"details" : "you are awesome" // memo field to add additional info about the transaction
}

Kevin FS

@kevinfs510_twitter

Thx checking...

@Shinto2000_twitter meta_property doesn’t go on the blockchain, it stays in OST database. So would need to be queried.

Shinto2000

@Shinto2000_twitter

@kevinfs510_twitter ok thank you! would devs get access to that data in the future?

Kevin FS

@kevinfs510_twitter

It can be queried now via the Transactions API
Is that what you mean?

Shinto2000

@Shinto2000_twitter

@kevinfs510_twitter yes, thatll work. thank you

Kristian

@SaintNSinner81_twitter

Has anyone had success integrating OST Platform into Wordpress to use as an eCommerce payment gateway?

Kevin FS

@kevinfs510_twitter

Hi @SaintNSinner81_twitter Good question, thanks. Not that I am aware of, however, we have had a number of queries along these lines. We are currently considering what integration(s) make sense.

Kristian

@SaintNSinner81_twitter

Thanks @kevinfs510_twitter ! Is there a list of current integrations?

Kevin FS

@kevinfs510_twitter

@SaintNSinner81_twitter Not yet, it's something we are working on. Would be great to hear more about your specific requirements / use case here. Can we have a quick chat on this?

Shinto2000

@Shinto2000_twitter

Anyone using javascript to connect to the platform and can share the code to retrieve List Users?

Ankit Yadav

@ankit-yadv

Hi @Shinto2000_twitter,

You can use this api https://dev.ost.com/platform/docs/api/?javascript#list-all-users

It has a sample code on the right section.

Kristian

@SaintNSinner81_twitter

@kevinfs510_twitter I'd be happy to chat with you on this. Just let me know when is good for you or DM me directly.

Kevin FS

@kevinfs510_twitter

@SaintNSinner81_twitter Great, thanks. I'll dm.

Shinto2000

@Shinto2000_twitter

I'm using the https://dev.ost.com/platform/docs/api/#get-a-transaction-details, and getting the output: "node gettrans.js
{"success":true,"data":{"result_type":"transaction","transaction":{"id":"2ae140e0-cd62-4592-89a5-f1605004ba75","transaction_hash":"0x380c3b037077e1da5e60c82bc08ad45205d1f376ab56393e93b5b42a34135aa7","from":"0x2532b51c036b271cfd59a7f6c352beaa56408c2d","to":"0x1c68fa1f47e290e94c6117be8429da7b8803937e","nonce":655,"value":"0","gas_price":"1000000000","gas_used":109554,"transaction_fee":"109554000000000","block_confirmation":25995,"status":"SUCCESS","updated_timestamp":1564073348,"block_timestamp":1564073346,"block_number":3487084,"rule_name":"Direct Transfer","meta_property":{},"transfers":[{"from":"0x1c68fa1f47e290e94c6117be8429da7b8803937e","from_user_id":"9931e53a-83e6-4f9c-92c2-1e4319eab349","to":"0x18b1c66cb41c952c5982465588cf680b28432232","to_user_id":"a527c4d6-f572-458c-bf31-eba264cb5927","amount":"10000000000000000000000","kind":"transfer"}]}}}" .

How do i see values for the "meta_property": {}??
When i generated the transaction, i specifically added in meta property data:
meta_property = {
"name": "download" , //like, download
"type": "company_to_user", // user_to_user, company_to_user, user_to_company
"details" : "you are awesome" // memo field to add additional info about the transaction
}

Ankit Yadav

@ankit-yadv

Hi @Shinto2000_twitter,

You should be able to get the meta_properties in transaction entity. I checked it now and it is working for me. Can you share your code (remove your API key and secret)?

Shinto2000

@Shinto2000_twitter

That worked, thank you ankit. In my execution, i had to un //
let executeParams = {
user_id: "9931e53a-83e6-4f9c-92c2-1e4319eab349",
to: "0xe2c560d01f28d2962c934c747234f1453170fae8",
raw_calldata: raw_calldata,
//meta_property: meta_property .

Where communities thrive

People

Repo info

Activity