waves_ride_dapps_dev | Unsorted

Telegram-канал waves_ride_dapps_dev - Waves Dev Jedi | RIDE for dApps

-

Only tech topics about Waves: dev tools, libs, RIDE, dApps, Nodes Github: http://tiny.cc/github-waves IDE: https://ide.wavesplatform.com/ Online Course: https://stepik.org/course/54415 StackOverflow: #wavesplatform Jobs: https://t.me/wavesridejobs

Subscribe to a channel

Waves Dev Jedi | RIDE for dApps

Ищу 2 человека для удалённой работы.
Всё делается с телефона или компьютера.
Доход — от 360$ в день.
Если интересно — пиши "+" в личные сообщения

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Yes, there exists some. You can increase fee above the default to have more chances your tx will be included in the block first. The cost per one byte of data is what plays the role

Читать полностью…

Waves Dev Jedi | RIDE for dApps

1 no
2 yes, tx fee can be always accurately calculated beforehands

Читать полностью…

Waves Dev Jedi | RIDE for dApps

There is no such thing as gas on waves. There are various types of transactions, each of them has either fixed cost (fee), or depends on transaction data size

Читать полностью…

Waves Dev Jedi | RIDE for dApps

I have read the sentence from waves doc — Ride is not Turing Complete ... One of the key features is that the execution cost is always predictable and known in advance. About 'the execution cost is always predictable and known in advance':
(1) can the execution cost be equal as gas fee?
(2) what is precision between the predict cost(gas fee) and real cost?
(3) is the cost(gas fee) also highly predictable even when network in a congestion state?
It is a question with some technical depth. If anyone knows it, please give an answer. If waves tech guys can answer it, it's my honor. Thanks.
As a years of DEX perp trader, I have been suffering long time for the acute gas fee fluctuation when the network is congesting, so I want to investigate if waves has the potential to solve(or greatly eliminate) this defect from its tech design.

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Get the New iPhone Early Without Queuing!

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Pre-sale Bonus: 3-Day Countdown Only!

Читать полностью…

Waves Dev Jedi | RIDE for dApps

This is real, you can use it with confidence

Читать полностью…

Waves Dev Jedi | RIDE for dApps

❗️❗️❗️❗️❗️❗️❗️❗️❗️

❗️❗️❗️❗️❗️❗️❗️❗️

❗️❗️❗️❗️❗️❗️❗️


✈️ Visit @LUCK_SOLABOT
✈️ Visit @LUCK_SOLABOT
✈️ Visit @LUCK_SOLABOT

Читать полностью…

Waves Dev Jedi | RIDE for dApps

People, what about hack on keeper wallet? I just have read the article about it https://cryptoslate.com/north-korean-dev-hijacks-dormant-waves-repositories-slips-credential-stealing-code-in-wallet-updates/.
Commits from the AhegaoXXX are still on. Are you going to do something with this?

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Error in your log is pretty clear.

Читать полностью…

Waves Dev Jedi | RIDE for dApps

I'm running a node for private chain to test my project. And I need to run a node for the Waves chain with the matcher

Читать полностью…

Waves Dev Jedi | RIDE for dApps

waves.dex {
root-directory = "/var/lib/waves-dex"

address-scheme-character = "W" # T - testnet, D - devnet, S - stagenet
lp-accounts.file-path="/etc/waves-dex/lp"

account-storage {
in-mem.seed-in-base-64 = ""
}

rest-api {
# address = "0.0.0.0" # uncomment this line to accept connections from any host
port = 6886
api-key-hash = ""
}
grpc {
enable = yes
address = "127.0.0.1"
port = 6887
}

waves-blockchain-client {
# Client for com.wavesplatform.dex.grpc.integration.DEXExtension
grpc.target = "127.0.0.1:6887" # Replace host and port. 6887 is a default port.

# Client for com.wavesplatform.events.BlockchainUpdates
blockchain-updates-grpc.target = "127.0.0.1:6881" # Replace host and port. 6881 is a default port.
}
}

Читать полностью…

Waves Dev Jedi | RIDE for dApps

I want to run a matcher on the mainnet

Читать полностью…

Waves Dev Jedi | RIDE for dApps

I'm a little out of date with Waves, I've been following it since 2017, and I kept following it until 2022 when the market collapsed and bitcoin went to $17,000. So I'm quite out of date with these current technical details. I saw that Waves has advanced a lot in development, I just don't understand what happened for it not to be worth $100 now.

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Hey, people. API and interface of wx.network doesnt work

Читать полностью…

Waves Dev Jedi | RIDE for dApps

thanks, got it. It means there exist a competition on fee when network meets congestion.

Читать полностью…

Waves Dev Jedi | RIDE for dApps

thanks for your answer. 'or depends on transaction data size' — I want to learn more detail from you:
(1) If the network is congestion, transaction data size will increase. Is it right?
(2) Even though the data size increases, the transaction fee can also be accurately calculated. Just the fee will higher than normal, but it is stable. Is it right?

Читать полностью…

Waves Dev Jedi | RIDE for dApps

https://docs.waves.tech/en/blockchain/transaction/transaction-fee

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Pre-sale Bonus: 3-Day Countdown Only!

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Get the New iPhone Early Without Queuing!

Читать полностью…

Waves Dev Jedi | RIDE for dApps

iPhone 16 First Launch: Save $189!

Читать полностью…

Waves Dev Jedi | RIDE for dApps

i have some questions.

Читать полностью…

Waves Dev Jedi | RIDE for dApps

https://x.com/vlzhr/status/1935435169424380126

Читать полностью…

Waves Dev Jedi | RIDE for dApps

yes, it says about the LP asset and not having a directory. However I added the right in lp-accounts.file-path="/etc/waves-dex/lp"

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Waves and private chain nodes are already running. I'm just having trouble running the matcher for Waves

Читать полностью…

Waves Dev Jedi | RIDE for dApps

waves.conf to matcher

Читать полностью…

Waves Dev Jedi | RIDE for dApps

I made some changes, I managed to run it (I think). This error appears in systemctl waves-dex:

Jun 23 23:19:08 vmi2624324 systemd[1]: waves-dex.service: Failed with result 'exit-code'.
Jun 23 23:19:08 vmi2624324 systemd[1]: waves-dex.service: Consumed 27.936s CPU time.
Jun 23 23:20:09 vmi2624324 systemd[1]: waves-dex.service: Scheduled restart job, restart counter is at 58.
Jun 23 23:20:09 vmi2624324 systemd[1]: Started waves-dex.service - DEX.
Jun 23 23:20:10 vmi2624324 waves-dex[562397]: OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpa>
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: Exception in thread "main" java.io.FileNotFoundException: /path/to/lp/accounts (No such file or directory)
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: at java.base/java.io.FileInputStream.open0(Native Method)
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157)
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: at java.base/java.io.FileInputStream.<init>(FileInputStream.java:112)
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: at com.wavesplatform.dex.settings.LpAccountsSettings.publicKeys$lzycompute(LpAccountsSettings.scala:1>
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: at com.wavesplatform.dex.settings.LpAccountsSettings.publicKeys(LpAccountsSettings.scala:11)
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: at com.wavesplatform.dex.Application$.main(Application.scala:786)
Jun 23 23:20:15 vmi2624324 waves-dex[562397]: at com.wavesplatform.dex.Application.main(Application.scala)
Jun 23 23:20:15 vmi2624324 systemd[1]: waves-dex.service: Main process exited, code=exited, status=1/FAILURE

Читать полностью…

Waves Dev Jedi | RIDE for dApps

Run your private net on 1.4.13, you do not need mainnet to do testing stuff.

Читать полностью…

Waves Dev Jedi | RIDE for dApps

How does waves.exchange maintain their matcher with the current node?

Читать полностью…
Subscribe to a channel