I am not talking about my account in particular, only about red paint as a whole.

Thought it will be dismissed or something and the flags will take the place, but paint is still there and TBH nothing changed about paint.

I was sure this will be the end of the red paint threat, that someday an angry DT member will paint me and ruin my account because he doesn't like me or has nothing better to do.

I don't really see anyone satisfied with the new trust system here. At the beginning, I thought that it will take some time and everything will work out, but unfortunately with the time passing, like others, I noticed serious shortcomings. Even started to write a thread about this subject to share my thoughts with you but I was afraid that it is too controversial to be published. So I started to read the meta section (not a big fan of) and found that there are many threads about the problems and threats in the new trust system, like this one for example.

I was happy that finally there will be no way that one red paint will ruin somebody account, especially after I was mistrusted and almost lost my account two times.
To my surprise red paint is still here, still counts and now is even much easier to get it, because there are hundreds of DT members, which trust ratings counts as a valid once and give us nice red -1 in the account trust summary.

Sometimes I see red painted DT members and ask myself: "what is going on?", "how to trust such DT?". We all see that something has to be changed with paint and trust annotations, to take the power away from a single person. Just leave it as simple feedback and not a trust measure. There are so many negative annotations left, only because of personal wars and finally, we find ourselves in a situation, when a DT member has a hundred feedbacks of all kinds (bad and good) and there is no way to judge him based on this. I think flags are a nice feature and can be valuable. Of course first, something has to be done with all these problems.

A jaka cena za Ledger Nano X?

I want to be notified through PM in the forum:

1. Write a PM to Maggiordomo by placing in the subject subscribe.
2. Write in the body of PM notificationinterval:0.
3. Send  PM to Maggiordomo.



I want to be notified through Telegram:

1. Contact @Maggiordomo_Service_bot on telegram (with the same telegram username used for registering to the bot).
2. Write something to him in Telegram chat, example: start.



1. Write a PM here on Bitcointalk to Maggiordomo by placing in the subject subscribe.
2. Write in the body: telegram:yourTelegramUsername (doesn't matter if with @ or without)
3. Send PM to Maggiordomo.



I know this is obvious for many but as we see not tech-savvy members can be confused even with such a simple task. I already had to explain these setup to somebody step by step more than once. I hope this would be helpful.

Jeżeli rozmawiamy na prawdę o zarabianiu, to na wszystkich tych altach, aktualnie nie da się zarobić, nawet pasywnie, bo żeby to zrobić trzeba najpierw zainwestować, co przy stanie rynku kryptowalut w ostatnim roku, było i nadal jest z góry skazane na porażkę. Oczywiście jest kilka altów, które cenowo poszły do góry ale nie jest to żaden z wymienionych i nie wiem czy są to alty POS.

Trzeba by mieć ich wystarczająco dużo, żeby POS płacił jakieś godziwe stawki, które później można by sprzedać na giełdzie i faktycznie zarobić. Aktualnie nie jest to możliwe, bo wszystkie alty straciły na wartości nawet 99%, czyli trzymając je i czekając na nagrody z POS, tracisz aktualnie tak dużo, że to się nie opłaca. Jeżeli tendencja na rynku kryptowalut się odwróci i znowu ceny zaczną rosnąć lub chociaż przestaną spadać, to wtedy będzie można myśleć o kopaniu.

Oczywiście wymieniłeś parę dobrych projektów z potencjałem jak NEO, Decred i Qtum. Z nich wszystkich najbardziej skłaniam się ku Decred i Qtum. Jakoś nigdy nie rozumiałem tego azjatyckiego ethereum NEO i nie zainwestowałem w niego. Zawsze porównuję  go z Litecoinem, który od lat jest w czołówce ale nigdy nie zaskoczył ceną (jako copycat), chociaż moim zdaniem jest nawet lepszy aktualnie od Bitcoina. Myślę, że dużo ludzi postrzega NEO podobnie, jako copycat Ethereum.

Yes, you are correct and these browsers are still vulnerable. This is clear to see on the post I quoted above in OP with the fake Binance web page.

I will try to find additional information about these vulnerable browsers and maybe provide a solution if there is any and I will be able to find them.


Exactly is enough to adjust the settings in FF:



Google has already fixed this issue in Chrome Canary 59, and a permanent fix is from Chrome Stable 58.

As I said already I will do a research today and try to find solutions for vulnerable browsers and publish here in the thread.

As you see from the source links everybody calls these as transaction types and this is why I did the same. Everything has been explained in the OP, what is the script, transaction, etc, so I think there should be no problem with understanding what is what.


I provided all sources as always in the post footer, but here it is: https://learnmeabitcoin.com/glossary/p2ms





Thanks for FTFY but to be honest I cut these sentences by myself to make it shorter and easy to understand. As you see this is in the first part for beginners.

Of course, I should do it properly, without changing the meaning completely and I thought is ok but added your corrections too.


Members advised above to make it shorter, so I did it and removed a couple of additional sentences. I have talked about this in my post above, that I found it really hard and to be honest this article was a lot longer in original form. I had to make compromises and cut out all I found or thought is not so important, but everything is important here and that is why I will update this thread further. Don't want to write more in the OP, only add all additional information in the posts during the discussion. Just like now.

You are right I checked this one more time and see that indeed we are talking about two different coins here.

Both are related to exchanges and that is why I was sure is the same one.

If anyone has a link to a page like CMC with Dexage token information then please share.

UPDATED 4.12.2023

Punycoder - Punycode converter or an IDN converter, a tool for Punycode to Text/Unicode and vice-versa conversion.

---

Punycode - system for converting words that can't be written in ASCII (American Standard Code for Information Interchange), such as in Ancient Greek the phrase ΓNΩΘIΣEAYTON, once converted into ASCII characters, looks like this: xn--mxadglfwep7amk6b. This conversion system allows International Domain Names (IDNs), which include non-ASCII characters, to be displayed using only the Roman letters A to Z, the digits 0 to 9 and the hyphen (-) character.

Punycode is useful, because the world-wide Domain Name System (DNS), which turns readable server names into computer-friendly network numbers, can only recognize limited subset of ASCII characters in domain names. Some of the letters in the Roman alphabet are the same shape as letters in the Greek and other alphabets. Examples are the letters I, E, A, Y, T, O, and N.



A malicious site can imitate a legitimate URL and display it which leaves us with very few ways to tell if we are being tricked by an imposter. Attackers who trick people into loading the fake page can easily obtain personal information because the site is an exact copy of original one.

Many years ago, the Internet Corporation for Assigned Names and Numbers (ICANN) allowed non-ASCII (Unicode) characters to be included in web domains. It didn't take long for them to realize that this decision was going to cause problems. Certain characters from different languages can be confused for Unicode since they look the same when displayed in a browser. This is used as a tool by cybercriminals to spoof URLs and target unsuspecting victims.



To counteract the issue, ICANN developed Punycode as a way of specifying actual domain registrations by representing Unicode within the limited character subset of ASCII used for internet hostnames. The idea was that browsers would first read the Punycode URL and then transform it into displayable Unicode characters inside the browser.

However, just like with Unicode, Punycode could also hide phishing attempts, using characters found in different languages. To combat this, Web browser vendors introduced add-on filters to render URLs as Punycode, instead of Unicode, if they contained characters from different languages.

Punycode Problems

By default, many web browsers use Punycode encoding to represent Unicode characters in the URL to defend against Homograph phishing attacks (where the website address looks legitimate, but is not, because a character or characters have been replaced deceptively with Unicode characters).

For example, the Chinese domain "短.co" is represented in Punycode as "xn--s7y.co" and the German city of "München" becomes in the Punycode "xn--mnchen-3ya" because the letter ü is not available in English. There are quite a few Unicode characters represented in alphabets such as Greek, Cyrillic, and Armenian, which look almost identical to Latin letters at a glance but are treated very differently by computers when resolving the different web addresses.

Homograph attacks - extremely difficult to detect based on their deployment method. Some of these steps will also protect you from other types of online attacks as well.

Example of Punycode Phishing (Homograph) attack:


Another great example of Punycode Homograph Phishing attack. This time Poloniex exchange is targeted. Just look at how similar it looks compared to the original page.



Difference between original page and malicious one is that the hacker misspelled the phrase "Sign in" as "Sing in" a couple of times.

also different in this attack is that the SSL certificate is shown as valid:



Not all browsers are vulnerable

Of all the browsers tested, three rendered the page using Unicode characters, as appӏe.com. These are Chrome, Firefox, and Opera.



Other browsers, such as Edge, Internet Explorer, Safari, Vivaldi, and Brave, did not render the page using Unicode characters and displayed the Punycode URL. There's a filter that checks if the Punycode URL is in the same character set as the user's default OS settings.



Google has already fixed this issue in Chrome Stable 58.

Preventing Homograph Phishing Attacks in Firefox

Firefox users can complete the following steps to manually apply temporary protection against Punycode Phishing (Homograph) attacks:

• Open a new tab in Firefox
• Type about:config in address bar and press Enter.
• Click the I accept the risk! button.
• Type Punycode in the search bar.
• A Preference Name titled: IDN_show_punycode will be displayed Right-Click and select Toggle to change the Value field from False to True.
• Close the about:config tab.

• Set Firefox to display Punycode names. See steps above for changing the about: config settings in Firefox.
• Click on the padlock to display the HTTPS certificate. This will show the domain name that the certificate was issued in ASCII-only format. If the name starts with xn it is a Punycode domain, no matter what it looks like in the address bar
• Check the legitimacy of URLs by copying them out of the web browser and pasting them into a text editor. A spoofed URL only appears legitimate, but it actually uses an address beginning with www.xn-- which will be revealed for what it actually is once taken outside the browser?s address bar.
• Use a Password Manager. The software will automatically enter in your login credentials for the actual domains they are linked to,
• Always manually type website URLs in the address bar for important sites like Gmail or banking websites, instead of clicking any link from a website or email.

Suspected Facebook phishing website, another Punycode Homograph Phishing attack.



This time is much easier to see that something is wrong with these Facebook pages, even for an untrained eye, because both of the SSL certificates are bad and displayed in red.



I hope that all these examples will help to identify Punycode phishing attacks. One has to check everything three times to be safe online today, there are no shortcuts. This is very scary and I already have been on such malicious websites, only thanks to my password manager and other tools I was able to identify them soon enough but to be honest nobody is safe. I see hackers getting better and more greedy every day.

Look at the list I gathered, with already known Punycode websites, for sure this is only a small percentage of what exists already. We have to imagine that every day hundreds of new phishing websites are created and we have to do all what possible to protect ourselves.


Punycode Domain Detection - developed by Phish.ai and released as Google Chrome extension that can detect when users are accessing domains spelled using non-standard Unicode characters and warn about the potential of a homograph attack.

---

Punycoder - Punycode converter or an IDN converter, tool for Punycode to Text/Unicode and vice-versa conversion.

Service called Gluee with multiple tools for webmasters and developers.


https://www.gluee.com/tools/

First one called Punycoder is a tool that converts text with special characters (UNICODE) to the Punycode encoding (just ASCII) and vice versa.

This is tool to check all suspicious Phishing Punycode URLs. Just copy and paste the needed link.


https://www.punycoder.com/

---

DON'T USE ANY OF THESE LINKS - MALICIOUS WEBSITES!!!

List of already known Punycode Phishing URLs:

ns1.xn--aobe-l6b.com.                 -->        ns1.aɗobe.com.
ns2.xn--aobe-l6b.com.                 -->        ns2.aɗobe.com.
mail.xn--adoe-x34a.com.               -->    mail.adoḅe.com.
xn--adob-yva.com.                     -->    adobė.com.
xn--adoe-x34a.com.                    -->    adoḅe.com.
xn--aobe-qua.com.                     -->    aďobe.com.
xn--dobe-p5b.com.                     -->    ɑdobe.com.

APPLE

mail.xn--pple-zna.com.                -->        mail.?pple.com.
ns1.xn--appl-ou5a.com.                -->        ns1.applẹ.com.
ns2.xn--appl-ou5a.com.                -->        ns2.applẹ.com.
www.xn--le-m1aa24e.com.               -->        www.ɑƿƿle.com.
www.xn--pple-9na.cf.                  -->        www.âpple.cf.
www.xn--ppl-hla7b.cf.                 -->        www.âppl?.cf.
xn--ppl-hla7b.cf.                     -->        âppl?.cf.
www.xn--app-mra30o.com.               -->        www.appɩė.com.
xn--aple-csa.com.                     -->        ap?le.com.
xn--appl-8va.com.                     -->        applę.com.
xn--appl-yva.com.                     -->        applė.com.
www.xn--le-m1aa24e.com.               -->        www.ɑƿƿle.com.

AMAZON

www.xn--amazo-7l1b.com.               -->        www.amazoṇ.com.
www.xn--amazo-vl1b.com.               -->        www.amazoṅ.com.
www.xn--amzon-ucc.com.                -->        www.amȧzon.com.
www.xn--mazon-2qa.de.                 -->        www.âmazon.de.
www.xn--mazon-2qa.eu.                 -->        www.âmazon.eu.
www.xn--mazon-wqa.com.                -->        www.ámazon.com.
www.xn--mzn-plab3i.com.               -->        www.ämäzön.com.
xn--amaon-6y1b.com.                   -->        amaẓon.com.
xn--amaon-7hb.com.                    -->        amaźon.com.
xn--amazo-sta.com.                    -->        amazo?.com.
xn--amazo-vl1b.com.                   -->        amazoṅ.com.
xn--amzon-sqa.com.                    -->        am?zon.com.
xn--amzon-ucc.com.                    -->        amȧzon.com.

BANK OF AMERICA

www.xn--bakofamerica-qfc.com.         -->        www.baŋkofamerica.com.
mail.xn--bnkofmeric-q5aef.com.        -->    mail.bänkofämericä.com.
secure.xn--bakofamerica-qfc.com.      -->    secure.baŋkofamerica.com.
www.xn--ankofamerica-70c.com.         -->    www.ƅankofamerica.com.
www.xn--bakofamerica-qfc.com.         -->    www.baŋkofamerica.com.
www.xn--banofamerica-p7b.com.         -->    www.banĸofamerica.com.
www.xn--bnkofamerica-pob.com.         -->    www.bąnkofamerica.com.
www.xn--bnkofmeric-ggeef.com.         -->    www.bɑnkofɑmericɑ.com.
www.xn--bnkofmeric-q5aef.com.         -->    www.bänkofämericä.com.
xn--ankofamerica-70c.com.             -->    ƅankofamerica.com.
xn--bakofamerica-qfc.com.             -->    baŋkofamerica.com.
xn--banofamerica-p7b.com.             -->    banĸofamerica.com.
xn--bnkofamerica-pob.com.             -->    bąnkofamerica.com.
xn--bnkofmeric-ggeef.com.             -->    bɑnkofɑmericɑ.com.
xn--bnkofmeric-q5aef.com.             -->        bänkofämericä.com.

BITTREX

xn--bitrex-rkb.com.                   -->        bitţrex.com.
xn--bittex-zx7b.com.                  -->        bittṛex.com.
xn--bittrx-7ua.com.                   -->        bittr?x.com.
www.xn--bitrex-rkb.com.               -->        www.bitţrex.com.
www.xn--bittrx-7ua.com.               -->        www.bittr?x.com.
xn--ittrex-hrb.com.                   -->        ƅittrex.com.
www.xn--ittrex-hrb.com.               -->        www.ƅittrex.com.
xn--bttx-vpa4unq.com                  -->        bíttŕēx.com
CISCO

xn--csco-lza.com.                     -->        cısco.com.
xn--csco-qpa.com.                     -->        c?sco.com.
xn--csco-vpa.com.                     -->        císco.com.
xn--n1afa3fe.net.                     -->        cisco.net.

COINBASE

xn--cinbase-10a.com.                  -->         c?inbase.com.
xn--cinbase-90a.com.                  -->         cöinbase.com.
xn--cinbase-d0a.com.                  -->         c?inbase.com.
xn--cinbase-t0a.com.                  -->         côinbase.com.
xn--coibase-6za.com.                  -->         coi?base.com.
xn--coibase-r13c.com.                 -->         coiṇbase.com.
xn--coinbae-fqb.com.                  -->         coinbaşe.com.
xn--coinbas-8xa.com.                  -->         coinbas?.com.
xn--coinbas-pya.com.                  -->         coinbas?.com.
xn--coinbas-z8a.com.                  -->         coinbasė.com.
xn--coinbse-9wa.com.                  -->         coinbäse.com.
xn--coinbse-lwa.com.                  -->         coinbáse.com.
xn--conbase-0ya.com.                  -->         co?nbase.com.
xn--conbase-feb.com.                  -->         coīnbase.com.
xn--conbase-hza.com.                  -->         coînbase.com.
xn--conbase-pza.com.                  -->         co?nbase.com.
xn--conbase-sfb.com.                  -->         coınbase.com.
xn--oinbase-l5a.com.                  -->         ĉoinbase.com.
xn--oinbase-txa.com.                  -->         çoinbase.com.

CREDIT SUISSE

xn--crditsuisse-cbb.at.               -->         créditsuisse.at.
xn--crditsuisse-cbb.ch.               -->         créditsuisse.ch.
xn--crditsuisse-cbb.com.              -->         créditsuisse.com.
xn--crditsuisse-cbb.de.               -->         créditsuisse.de.
xn--crditsuisse-cbb.dk.               -->         créditsuisse.dk.
xn--crditsuisse-cbb.eu.               -->         créditsuisse.eu.
xn--crditsuisse-cbb.net.              -->         créditsuisse.net.
xn--crdit-suisse-ceb.at.              -->         crédit-suisse.at.
xn--crdit-suisse-ceb.ch.              -->         crédit-suisse.ch.
xn--crdit-suisse-ceb.com.             -->         crédit-suisse.com.
xn--crdit-suisse-ceb.de.              -->         crédit-suisse.de.
xn--crdit-suisse-ceb.dk.              -->         crédit-suisse.dk.
xn--crdit-suisse-ceb.net.             -->         crédit-suisse.net.
xn--credit-sisse-klb.com.             -->         credit-süisse.com.

EBAY

xn--bay-ema.com.                      -->         ?bay.com.
xn--eby-fla.com.                      -->         ebáy.com.
xn--eby-bla.com.                      -->         eb?y.com.
xn--eby-hsb.com.                      -->         ebɑy.com.
xn--eby-jla.com.                      -->         ebây.com.
xn--80aj7b8a.com.                     -->         eьay.com.

FACEBOOK

www.xn--acebook-js3c.com.             -->         www.ḟacebook.com.
www.xn--acebook-w1b.net.              -->         www.?acebook.net.
www.xn--aceook-dg7b2i.com.            -->         www.ḟaceḃook.com.
xn--acebook-js3c.com.                 -->         ḟacebook.com.
xn--aceook-dg7b2i.com.                -->         ḟaceḃook.com.
xn--faboo-5xa8ftm.eu.                 -->         faċėbooķ.eu.
xn--fabook-qva9w.eu.                  -->         faċëbook.eu.
xn--facboo-k4a3x.eu.                  -->         facėbooķ.eu.
xn--facbook-4xa.com.                  -->         fac?book.com.
xn--facbook-lya.fr.                   -->         fac?book.fr.
xn--facbook-v8a.eu.                   -->         facėbook.eu.
xn--facebok-50a.fr.                   -->         faceb?ok.fr.
xn--facebok-60a.tk.                   -->         facebo?k.tk.
xn--facebok-h0a.eu.                   -->         faceb?ok.eu.
xn--facebok-x0a.fr.                   -->         facebôok.fr.
xn--faceboo-jhb.com.                  -->         facebooĸ.com.
xn--faceboo-jhb.net.                  -->         facebooĸ.net.
xn--faceook-pm3c.com.                 -->         faceḅook.com.
xn--faebok-xua7j.fr.                  -->         façeboök.fr.
xn--faebook-35a.com.                  -->         faċebook.com.
xn--fcbook-w0a9l.eu.                  -->         fącėbook.eu.
xn--fcebook-8va.com.                  -->         f?cebook.com.
xn--fceboo-w0a91b.eu.                 -->         fącebooķ.eu.
www.xn--fabook-41a0h.eu.              -->         www.faċėbook.eu.
www.xn--fabook-xua89a.eu.             -->         www.façėbook.eu.
www.xn--facebok-60a.tk.               -->         www.facebo?k.tk.
www.xn--facebok-e1a.com.              -->         www.faceböok.com.
www.xn--facebok-h0a.fr.               -->         www.faceb?ok.fr.
www.xn--facebok-i0a.eu.               -->         www.facebo?k.eu.
www.xn--faceok-sg7bq0e.com.           -->         www.faceḅọok.com.
www.xn--faceook-1yb.com.              -->         www.faceƅook.com.
www.xn--faebook-35a.com.              -->         www.faċebook.com.
www.xn--faebook-64a.eu.               -->         www.faćebook.eu.
www.xn--fcebook-s3a.tk.               -->         www.fācebook.tk.
m.xn--80akppap2f62a.com.              -->         m.ғaceьooк.com.
xn--80akppap2f62a.com.                -->         ғaceьooк.com.

GOOGLE

www.xn--oole-9pb06e.com.              -->        www.ǥooɡle.com.
ww25.xn--gogle-uob.com.               -->        ww25.gơogle.com.
xn--ggle-lqaa.com.                    -->        g??gle.com.
xn--gogl-1nd42e.com.                  -->        google.com.
xn--gogle-7ta.com.                    -->        goôgle.com.
xn--gogle-jua.com.                    -->        göogle.com.
xn--gogle-kua.com.                    -->        goögle.com.
xn--gogle-uta.com.                    -->        g?ogle.com.
xn--gogle-vob.com.                    -->        goơgle.com.
xn--googl-n0a.com.                    -->        googlę.com.
xn--oogl-epa71n.com.                  -->        ǵooglé.com.
xn--oogle-v1a.xyz.                    -->        ġoogle.xyz.
xn--oole-9pb06e.com.                  -->        ǥooɡle.com.
www.xn--ggl-8la1ca.com.               -->        www.g??gl?.com.
www.xn--ggle-lqaa.com.                -->        www.g??gle.com.
www.xn--gogle-uta.com.                -->        www.g?ogle.com.
www.xn--googl-n0a.com.                -->        www.googlę.com.

KRAKEN

xn--80afhrc5a.com.                    -->    кгaкeп.com.
xn--krken-nra.com.                    -->    kr?ken.com.
xn--raken-gnb.com.                    -->    ƙraken.com.
xn--raken-n5a.com.                    -->    ķraken.com.

MICROSOFT

ww8.xn--mcrosoft-tkb.com.             -->        ww8.mıcrosoft.com.
www.xn--mcrosoft-c2a.es.              -->        www.mícrosoft.es.
windows.xn--mcrosoft-c2a.com.         -->    windows.mícrosoft.com.
ww8.xn--mcrosoft-tkb.com.             -->    ww8.mıcrosoft.com.
www.xn--icrosoft-g89c.com.            -->    www.ṃicrosoft.com.
www.xn--mcosoft-rfb211a.com.          -->    www.mıcɾosoft.com.
www.xn--mcrosof-7ya00i.com.           -->    www.mícrosofť.com.
www.xn--mcrosoft-21a.ch.              -->    www.m?crosoft.ch.
www.xn--mcrosoft-21a.com.             -->    www.m?crosoft.com.
www.xn--mcrosoft-21a.eu.              -->    www.m?crosoft.eu.
www.xn--mcrosoft-21a.fr.              -->    www.m?crosoft.fr.
www.xn--mcrosoft-9ib.com.             -->    www.mīcrosoft.com.
www.xn--mcrosoft-c2a.com.             -->    www.mícrosoft.com.
www.xn--mcrosoft-c2a.de.              -->    www.mícrosoft.de.
www.xn--mcrosoft-c2a.es.              -->    www.mícrosoft.es.
www.xn--mcrosoft-c2a.eu.              -->    www.mícrosoft.eu.
www.xn--mcrosoft-g80d.com.            -->    www.mịcrosoft.com.
www.xn--mcrosoft-l2a.com.             -->    www.mîcrosoft.com.
www.xn--mcrosoft-tkb.com.             -->    www.mıcrosoft.com.
www.xn--mcrosoft-tkb.de.              -->    www.mıcrosoft.de.
www.xn--mcrosoft-u2a.com.             -->    www.m?crosoft.com.
www.xn--microsft-03a.com.             -->    www.microsóft.com.
www.xn--microsft-9fd.com.             -->    www.microsȯft.com.
www.xn--microsot-ez9c.com.            -->    www.microsoḟt.com.
www.xn--microsot-x9b.com.             -->    www.microso?t.com.
www.xn--micrsoft-y3a.com.             -->    www.micrósoft.com.
xn--icrosoft-g89c.com.                -->    ṃicrosoft.com.
xn--mcosoft-rfb211a.com.              -->    mıcɾosoft.com.
xn--mcrosof-7ya00i.com.               -->    mícrosofť.com.
xn--mcrosoft-21a.ch.                  -->    m?crosoft.ch.
xn--mcrosoft-21a.com.                 -->    m?crosoft.com.
xn--mcrosoft-21a.eu.                  -->    m?crosoft.eu.
xn--mcrosoft-21a.fr.                  -->    m?crosoft.fr.
xn--mcrosoft-9ib.com.                 -->    mīcrosoft.com.
xn--mcrosoft-c2a.com.                 -->    mícrosoft.com.
xn--mcrosoft-c2a.de.                  -->    mícrosoft.de.
xn--mcrosoft-c2a.es.                  -->    mícrosoft.es.
xn--mcrosoft-g80d.com.                -->    mịcrosoft.com.
xn--mcrosoft-l2a.com.                 -->    mîcrosoft.com.
xn--mcrosoft-tkb.com.                 -->    mıcrosoft.com.
xn--mcrosoft-tkb.de.                  -->    mıcrosoft.de.
xn--mcrosoft-u2a.com.                 -->    m?crosoft.com.
xn--micosoft-i0d.com.                 -->    micɾosoft.com.
xn--microoft-l9c.com.                 -->    microșoft.com.
xn--microsft-03a.com.                 -->    microsóft.com.
xn--microsft-9fd.com.                 -->    microsȯft.com.
xn--microsof-eyb.com.                 -->    microsofť.com.
xn--microsof-hk0d.com.                -->    microsofṭ.com.
xn--microsot-ez9c.com.                -->    microsoḟt.com.
xn--microsot-x9b.com.                 -->    microso?t.com.
xn--micrsoft-y3a.com.                 -->    micrósoft.com.

NETFLIX

xn--etflix-vwa.com.                   -->        ?etflix.com.
www.xn--netflx-0va.com.               -->        www.netfl?x.com.
ns1.xn--ntflix-iva.com.               -->    ns1.n?tflix.com.
ns2.xn--ntflix-iva.com.               -->    ns2.n?tflix.com.
ww1.xn--etflix-vwa.com.               -->    ww1.?etflix.com.
ww35.xn--etflix-vwa.com.              -->    ww35.?etflix.com.
ww8.xn--etflix-vwa.com.               -->    ww8.?etflix.com.
www.xn--etflix-vwa.com.               -->    www.?etflix.com.
www.xn--netflx-0va.com.               -->    www.netfl?x.com.
www.xn--netflx-7va.com.               -->    www.netflíx.com.
www.xn--netflx-7va.eu.                -->    www.netflíx.eu.
www.xn--netflx-f9a.com.               -->    www.netflįx.com.
www.xn--netflx-mwa.com.               -->    www.netfl?x.com.
www.xn--netflx-t9a.com.               -->    www.netflıx.com.
www.xn--netlix-5tb.com.               -->    www.net?lix.com.
www.xn--ntflix-bva.com.               -->    www.nétflix.com.
www.xn--ntflix-i4a.com.               -->    www.nėtflix.com.
www.xn--ntflix-iva.com.               -->    www.n?tflix.com.
xn--etflix-vwa.com.                   -->    ?etflix.com.
xn--netflx-0va.com.                   -->    netfl?x.com.
xn--netflx-7va.com.                   -->    netflíx.com.
xn--netflx-7va.eu.                    -->    netflíx.eu.
xn--netflx-f9a.com.                   -->    netflįx.com.
xn--netflx-mwa.com.                   -->    netfl?x.com.
xn--netflx-t9a.com.                   -->    netflıx.com.
xn--netlix-5tb.com.                   -->    net?lix.com.
xn--ntflix-bva.com.                   -->    nétflix.com.
xn--ntflix-i4a.com.                   -->    nėtflix.com.
xn--ntflix-iva.com.                   -->    n?tflix.com.

NEW YORK TIMES

xn--nytmes-5va.com.                   -->    nytímes.com.
xn--nytmes-dwa.com.                   -->    nytîmes.com.
xn--nytmes-yk8b.com.                  -->    nytỉmes.com.
xn--nytmes-yva.com.                   -->    nyt?mes.com.
xn--ytimes-vwa.com.                   -->    ?ytimes.com.
POLONIEX

xn--polonex-3ya.com.                  -->       polon?ex.com.
xn--oloiex-yt7b2e.com.                -->   ṗoloṇiex.com.
xn--oloniex-c53c.com.                 -->   ṗoloniex.com.
xn--plonex-6va6c.com.                 -->   pôloníex.com.
xn--ploniex-l0a.com.                  -->   póloniex.com.
xn--polniex-ex4c.com.                 -->   polọniex.com.
xn--polniex-n0a.com.                  -->   polóniex.com.
xn--poloiex-s13c.com.                 -->   poloṇiex.com.
xn--polonex-cza.com.                  -->   poloníex.com.
xn--polonex-ffb.com.                  -->   polonįex.com.
xn--polonex-ieb.com.                  -->   polonīex.com.
xn--polonex-kza.com.                  -->   polonîex.com.
xn--polonex-sza.com.                  -->   polon?ex.com.
xn--polonex-vfb.com.                  -->   polonıex.com.
xn--polonex-zw4c.com.                 -->   polonịex.com.
xn--polonix-ws4c.com.                 -->   poloniẹx.com.
xn--polonix-y8a.com.                  -->   poloniėx.com.
xn--pooniex-ojb.com.                  -->   połoniex.com.

TWITTER

www.xn--twittr-7ua.tv.                -->        www.twitt?r.tv.
www.xn--twittr-mva.tv.                -->        www.twitt?r.tv.
www.xn--twittr-tva.net.               -->        www.twittër.net.
www.xn--twtter-4va.net.               -->        www.twítter.net.
xn--twtter-cwa.com.                   -->        twîtter.com.
xn--twtter-q9a.net.                   -->        twıtter.net.
xn--twttr-7raz.com.                   -->        tw?tt?r.com.
xn--e1azaa2a9b5b.com.                 -->        тшiттeя.com.

WALMART

xn--wlmart-ita.com.                   -->        w?lmart.com.
xn--walmrt-lta.com.                   -->        walm?rt.com.
xn--wlmart-bua.com.                   -->        wälmart.com.
xn--wlmart-ita.com.                   -->        w?lmart.com.
xn--wlmart-pta.com.                   -->        wálmart.com.

WELLSFARGO

xn--wellsfarg-3mc.com.                -->        wellsfargơ.com.
xn--wellsfarg-e7a.com.                -->        wellsfargó.com.
xn--wellsfarg-tl7d.com.               -->        wellsfargọ.com.
xn--wellsfrgo-51a.com.                -->        wellsfárgo.com.

YAHOO

news.xn--yah-inaa.es.                 -->        news.yahóó.es.
news.xn--yaho-7qa.biz.                -->        news.yahöo.biz.
news.xn--yaho-7qa.info.               -->        news.yahöo.info.
news.xn--yaho-8qa.biz.                -->        news.yahoö.biz.
news.xn--yaho-nqa.com.                -->        news.yah?o.com.
news.xn--yaho-sqa.es.                 -->        news.yahóo.es.
news.xn--yaho-tqa.es.                 -->        news.yahoó.es.
news.xn--yaho-tqa.org.                -->        news.yahoó.org.
news.xn--yah-unaa.biz.                -->        news.yahöö.biz.
news.xn--yah-unaa.info.               -->        news.yahöö.info.
test.xn--yaho-7qa.biz.                -->        test.yahöo.biz.
test.xn--yaho-7qa.de.                 -->        test.yahöo.de.
test.xn--yaho-8qa.biz.                -->        test.yahoö.biz.
test.xn--yaho-8qa.info.               -->        test.yahoö.info.
test.xn--yaho-sqa.org.                -->        test.yahóo.org.
test.xn--yaho-tqa.com.                -->        test.yahoó.com.
test.xn--yaho-tqa.es.                 -->        test.yahoó.es.
test.xn--yaho-tqa.org.                -->        test.yahoó.org.
test.xn--yaho-yqa.com.                -->        test.yahoô.com.
test.xn--yah-unaa.info.               -->        test.yahöö.info.
wp.xn--yah-inaa.org.                  -->        wp.yahóó.org.
wp.xn--yaho-7qa.biz.                  -->        wp.yahöo.biz.
wp.xn--yaho-7qa.de.                   -->        wp.yahöo.de.
wp.xn--yaho-8qa.biz.                  -->        wp.yahoö.biz.
wp.xn--yaho-8qa.de.                   -->        wp.yahoö.de.
wp.xn--yaho-8qa.info.                 -->        wp.yahoö.info.
wp.xn--yaho-nqa.com.                  -->        wp.yah?o.com.
wp.xn--yaho-tqa.org.                  -->        wp.yahoó.org.
wp.xn--yaho-yqa.com.                  -->        wp.yahoô.com.
ww8.xn--yaho-yqa.com.                 -->        ww8.yahoô.com.
www.xn--yah-inaa.es.                  -->        www.yahóó.es.
www.xn--yah-inaa.org.                 -->        www.yahóó.org.
www.xn--yaho-7qa.biz.                 -->        www.yahöo.biz.
www.xn--yaho-7qa.de.                  -->        www.yahöo.de.
www.xn--yaho-7qa.info.                -->        www.yahöo.info.
www.xn--yaho-8qa.biz.                 -->        www.yahoö.biz.
www.xn--yaho-8qa.info.                -->        www.yahoö.info.
www.xn--yaho-nqa.com.                 -->        www.yah?o.com.
www.xn--yaho-ogb.com.                 -->        www.yahoơ.com.
www.xn--yaho-tqa.com.                 -->        www.yahoó.com.
www.xn--yaho-tqa.es.                  -->        www.yahoó.es.
www.xn--yaho-x0b.com.                 -->        www.yahȯo.com.
www.xn--yah-unaa.biz.                 -->        www.yahöö.biz.
www.xn--yah-unaa.info.                -->        www.yahöö.info.
www.xn--yaoo-674a.com.                -->        www.yaḣoo.com.
www.xn--yaoo-6xa.com.                 -->        www.yaħoo.com.
xn--ahoo-4ra.com.                     -->        ýahoo.com.
xn--yah-inaa.es.                      -->        yahóó.es.
xn--yaho-7qa.biz.                     -->        yahöo.biz.
xn--yaho-7qa.info.                    -->        yahöo.info.
xn--yaho-8qa.info.                    -->        yahoö.info.
xn--yaho-nqa.com.                     -->        yah?o.com.
xn--yaho-ogb.com.                     -->        yahoơ.com.
xn--yaho-sqa.org.                     -->        yahóo.org.
xn--yaho-tqa.es.                      -->        yahoó.es.
xn--yaho-tqa.org.                     -->        yahoó.org.
xn--yaho-x0b.com.                     -->        yahȯo.com.
xn--yaho-yqa.com.                     -->        yahoô.com.
xn--yah-unaa.biz.                     -->        yahöö.biz.
xn--yah-unaa.info.                    -->        yahöö.info.
xn--yhoo-0na.com.                     -->        y?hoo.com.
xn--yhoo-loa.info.                    -->        yähoo.info.
xn--yho-qla5g.info.                   -->        yähöo.info.
xn--yho-qla6g.info.                   -->        yähoö.info.

WIKIPEDIA

xn--wiipedia-nmb.com.                 -->    wiĸipedia.com.
xn--wikipdia-50a.cat.                 -->    wikip?dia.cat.
xn--wikipdia-f1a.com.                 -->    wikipédia.com.
xn--wikipdia-f1a.net.                 -->    wikipédia.net.
xn--wikipdia-f1a.org.                 -->    wikipédia.org.
xn--wikipeda-81a.com.                 -->    wikiped?a.com.
xn--wikipeda-i2a.org.                 -->    wikipedía.org.
xn--wikpedia-e2a.org.                 -->    wikípedia.org.
xn--wkipeda-rfbf.com.                 -->    wıkipedıa.com.
xn--wkipedia-c2a.org.                 -->    wíkipedia.org.
xn--wkipedia-u2a.com.                 -->    w?kipedia.com.
xn--wkpedia-7yab.org.                 -->    wíkípedia.org.
xn--wkpedia-rfbb.com.                 -->    wıkıpedia.com.
xn--wkpedia-zyab.com.                 -->    w?k?pedia.com.

YANDEX

www.xn--yande-vx1b.com.               -->        www.yandeẋ.com.
www.xn--yanex-vb1b.com.               -->        www.yanḋex.com.
www.xn--yndex-0jc.com.                -->        www.yɑndex.com.
xn--yande-uze.ru.ru.                  -->        yandex.ru.ru.
xn--yndex-3wa.com.                    -->        yąndex.com.

YOUTUBE

xn--yotube-jnb.com.                   -->        yoűtube.com.
xn--youtub-nva.com.                   -->        youtub?.com.
xn--youtue-7g7b.com.                  -->        youtuḇe.com.
ww11.xn--yotube-jya.com.              -->        ww11.yo?tube.com.
ww43.xn--yotube-4ya.com.              -->        ww43.yoütube.com.
www.xn--yotube-4ya.com.               -->        www.yoütube.com.
www.xn--youtue-7g7b.com.              -->        www.youtuḇe.com.
www.xn--youube-kmc.com.               -->        www.youțube.com.
xn--outube-9ya.com.                   -->        ýoutube.com.
www.xn--outube-9s8b.com.              -->        www.ỳoutube.com.
www.xn--outube-9ya.de.                -->        www.ýoutube.de.
MISC: LUXURY BRANDS

www.xn--gucc-tpa.com.                 -->        www.gucc?.com.
xn--gucc-tpa.com.                     -->        gucc?.com.
xn--herms-7ra.com.                    -->        herm?s.com.
www.xn--herms-7ra.fr.                 -->        www.herm?s.fr.
www.xn--lousvuitton-qcb.com.          -->        www.louísvuitton.com.

MISC: SOCIAL PLATFORMS

xn--nstagram-11a.com.                 -->        ?nstagram.com.
xn--nstagram-skb.com.                 -->        ınstagram.com.
www.xn--nstagram-skb.com.             -->        www.ınstagram.com.
xn--istagram-7pb.com.                 -->        iņstagram.com.
www.xn--imgu-t4a.com.                 -->        www.imguŕ.com.
xn--imgr-sra.com.                     -->        imgúr.com.
xn--whatspp-lwa.com.          &n

---

article used as a source for information:
https://www.bleepingcomputer.com/news/security/chrome-extension-detects-url-homograph-unicode-attacks/

Such a summary was needed at the end of this topic, exactly when I wanted to ask about the time difference between synchronization on HDD and SDD.

I think 2 days is acceptable, taking into consideration slow internet, sync can be possibly improved to 24 hours or even less on really good performing machines.

Still, I am surprised that there is no other way to sync faster. I was sure this is possible with the help of bootstrap files but maybe not for Bitcoin Core client?

When three high-rank members suggest that something needs to be changed or simplified, there is no point in discussing, only one has to do it, so I thought a bit and came to the conclusion that I will divide this article into two parts for less and more advanced users. So far I've added this:


Of course, I will Null Data and Non-standard transactions to this shortlist when I write it finally. What you think is better now?

That's the problem that there is no way to simplify this text further.

I did all what possible to make it short and informative and still, I had to remove many interesting details about Bitcoin transactions and their particular types.

This subject was already discussed in the Bitcoin Technical Support board and I thought it could be good for beginners, especially if they desire to learn something new or expand the knowledge about Bitcoin transactions.

Additionally, I counted on moderators, that they will move this thread if this board is not the best choice and on members like you, who will comment this.

I think I will leave it here for a while and if there will be more comments to move it to Bitcoin Technical Discussion, then I will do it or let mods decide in the end.

I will try to add frequently multiple actualizations and additional information to this thread about the transaction types, starting from the oldest one and pushing forward to the latest developments. I didn't know or haven't expected that this subject will be so comprehensive and I had to skip a lot of useful information about particular addresses to keep the OP in an interesting form which is not too long, because as we know, long once tire us very quickly and don't work so god as much shorter/compressed articles.

If there are any questions about the addresses or suggestions regarding the thread itself, please be so kind and let me know in the comments. I will try to answer all questions and frequently update the thread with additional info, like: how the particular scripts look like, how they look like, are built or how many transactions from each kind we have actually? As I said before there are hundreds of topics to discuss regarding Bitcoin addresses.

From what I have heard, yes, a few members reported that their tokens were locked and they had to contact the DEEX team to unlock them to be able to trade.

DEEX is an exchange so you can trade this token there I assume but if not they are already listed on Sistemcoin and BTC Alpha exchange from what I see on CMC.



https://coinmarketcap.com/currencies/deex/#markets

To understand how Bitcoin transactions work and what are their types, we have to start from the beginning and explain what Bitcoin addresses, transactions, scripts are and how they work?

Bitcoin address - is a string of alphanumerical characters that user can distribute to anyone who wishes to send them money. Bitcoin addresses can come in different formats, with common ones being: Pay-to-PubKeyHash (P2PKH) and Pay-to-ScriptHash (P2SH). Although anyone can send bitcoins to any given Bitcoin address, those funds can only be spent if they fulfill certain requirements laid out by Bitcoin’s scripting system.

Script - is effectively a list of recorded instructions that accompany each executed transaction; the script governs how the next person wanting to spend the sent bitcoins can gain access to them.
Scripts accompanying outputs in transactions are called PubKey Scripts (they are also known as locking scripts), which are known in code as scriptPubKey. Recipients of the sent bitcoins will then generate a signature script (also known as an unlocking script), which is a collection of data parameters that are generated by the spender which is used to satisfy a PubKey Script. Signature scripts are called scriptSig in code.

Example: when Alice decides to initiate a transaction with Bob, the output contains bitcoins that are spendable on condition that the instructions laid out by the attached PubKey Script are satisfied. Once this transaction is broadcasted and added to the blockchain, the network will categorize the transaction as an Unspent Transaction Output (UTXO), and Bob’s wallet software will recognize it as being a spendable balance. When Bob decides to spend this UTXO he will create an input that includes a signature script that must satisfy the conditions that Alice placed in the previous output’s PubKey Script.

Bitcoin transaction - is a transfer of value between Bitcoin wallets that gets included in the blockchain. Bitcoin wallets keep a secret piece of data called a private key or seed, which is used to sign transactions, providing a mathematical proof that they have come from the owner of the wallet. The signature also prevents the transaction from being altered by anybody once it has been issued. All transactions are broadcast to the network and usually begin to be confirmed within 10-20 minutes, through a process called mining. All transactions are visible in the blockchain and can be viewed with an explorer. A blockchain explorer is a site where every transaction included within the blockchain can be viewed in human-readable terms. This is useful for seeing the technical details of transactions in action and for verifying payments.

What are the Bitcoin Transaction types?

There a few standard Bitcoin transaction types at the time of writing. The developers behind Bitcoin have been continuously evolving the types of transactions to allow more functionality – the present list may change in the future. There are standard transactions which are accepted by the standard client – although some miners will accept the last type, which is a non-standard transaction but for a price.

Script > P2PK, P2PKH, P2MS, P2SH, P2WPKH, NULL DATA, NON-STANDARD



Standard types of transaction scripts: pay-to-public-key-hash (P2PKH), public-key (P2PK), multi-signature (P2MS) limited to 15 keys, pay-to-script-hash (P2SH), pay-to-witness-public-key-hash (P2WPKH) - This was a feature of Segwit which stands for Segregated Witness and data output Null Data (OP_RETURN), which are described in more detail in the following sections.
The last type is special and we call it a non-standard transaction.

Simplified explanation of transaction types for beginners.

P2PKH: "Pay To Public Key Hash" - This is how a big percentage of transactions are made. You are requiring the sender to supply a valid signature (from the private key) and public key. The transaction output script will use the signature and public key after checking the hash of the provided public key with previous output, and through some cryptographic functions will check if the signature is valid, if it was, then the funds will be spendable. This method conceals your public key in the form of a hash for extra security. If the spending condition is set to present a public key hash, then it is a P2PKH TX, and you have the std Op_Dup, Op_Hash160,... structure.

P2PK: "Pay To Public Key" - Unlike P2PKH that contained the hash of public key; this script contains the public key itself. Anyone using this method to send funds over the P2P network is showing people their public key in the transaction details. The spending condition only requires you to present your public key and signature. The public key would be recognized by your wallet (following the above mentioned coding scheme) as „type 1“ address.

P2SH: "Pay To Script Hash" - became a standard script in April 2012. The outputs of a transaction are just hash of scripts known as redeemscript that, if are executed with specific parameters, will result in a boolean of true or false. If a miner runs the output script with the supplied parameters and results in true, the money will be sent to your desired output. P2SH is used for multi-signature wallets making the output scripts logic that checks for multiple signatures before accepting the transaction. P2SH can also be used to allow anyone, or no one, to spend the funds. If the output script of a P2SH transaction is just 1 for true, then attempting to spend the output without supplying parameters will just result in 1 making the money spendable by anyone who tries. This also applies to scripts that return 0, making the output spendable by no one.

P2WPKH: "Pay To Witness Public Key Hash" - This was a feature of segwit which stands for Segregated Witness. Instead of using scriptSig parameters to check the transaction validity, there is a new part of the transaction called witness where the validity occurs. In 2015, Pieter Wuille introduced a new feature to bitcoin called Segregated Witness, also known by its abbreviated name, Segwit. Basically, Segregated Witness moves the proof of ownership from the scriptSig part of the transaction to a new part called the witness of the input.

P2MS: "MultiSignature" - (multisig) refers to requiring more than one key to authorize a Bitcoin transaction and was first applied to Bitcoin addresses in 2013. Generally used to divide up responsibility for possession of bitcoins. Standard transactions on the Bitcoin network could be called “single-signature transactions,” because transfers require only one signature — from the owner of the private key associated with the Bitcoin address. However, the Bitcoin network supports much more complicated transactions that require the signatures of multiple people before the funds can be transferred. These are often referred to as M-of-N transactions. The idea is that Bitcoins become “encumbered” by providing addresses of multiple parties, thus requiring cooperation of those parties in order to do anything with them. These parties can be people, institutions or programmed scripts. Became a standard script in January 2012.

NULL DATA: (OP_RETURN) - transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable pubkey script that full nodes don’t have to store in their UTXO database. Anyone can use a NULL DATA script to add some arbitrary data to a transaction, so you can find them scattered around the blockchain. We have to remember that not all miners accept transactions with null-data and not all nodes relay them. (OP_RETURN) outputsLook for empty outputs when browsing the blockchain, as NULL DATA scripts are almost always placed on empty outputs (because the outputs are made unspendable by the lock).
Here is a web page with a list of metadata recently embedded in the bitcoin blockchain using OP_RETURN outputs: http://coinsecrets.org/

Non-Standart - to include this type of transaction to the Bitcoin Blockchain, an agreement has to be reached with a miner: the non-standard transaction will be then included in the blockchain when the miner resolves the block. Depends on the hash rate from the miner it can be quite a while taking into consideration very high actual difficulty which is rising constantly from the start of Bitcoin. Of course, miner will take a proper fee for the non-standard transaction.



The addresses are generated from the hex pubkey a cool playground here:  http://gobittest.appspot.com/Address

---

Extended explanation of Bitcoin transaction types for more advanced users.

Pay-to-PubKey - (P2PK) is a simpler form of a bitcoin payment than pay-to-public-key-hash. With this script form, the public key itself is stored in the locking script, rather than a public-key-hash as with P2PKH earlier, which is much shorter. P2PK is a script pattern that locks an output to a public key. Despite being the simplest script for locking bitcoins to someone's public key, P2PK is not used as much as the similar (yet more complex) P2PKH script. This is because the original Bitcoin Core miner would use P2PK for the block reward when constructing a candidate block. You'll most commonly find P2PK in coinbase transactions in the earlier blocks in the blockchain.



Pay-to-Public-Key-Hash - (P2PKH) The vast majority of transactions processed on the bitcoin network were P2PKH transactions. These contain a locking script that encumbers the output with a public key hash, more commonly known as a bitcoin address. Transactions that pay a bitcoin address contain P2PKH scripts. An output locked by a P2PKH script can be unlocked (spent) by presenting a public key and a digital signature created by the corresponding private key.



P2PKH is the default script used by wallets when you want to "send" someone bitcoins, so you can find it in most blocks in the blockchain. This script pattern is used to "send" someone bitcoins. It's the most common script used for locking an output to someone's public key. It is similar to P2PK, but the lock contains the hash of a public key instead (and not the public key itself). Every time you send bitcoins to an address that starts with a 1 you are creating a P2PKH locking script.



Pay-to-ScriptHash - (P2SH) was introduced in Bitcoin Improvement Proposal 16 (BIP 16) by Gavin Andresen, and it resulted in a new ‘standard’ transaction type for the Bitcoin scripting system. The purpose of P2SH, according to Andresen: ‘Is to move the responsibility for supplying the conditions to redeem a transaction from the sender of the funds to the redeemer’.



In the example above, Bob generates a redeem script, hashes the redeem script to produce the redeem script hash and provides the hash to Alice. Alice can now then create a P2SH-style output containing Bob’s redeem script hash.

P2SH transaction type produces a number of advantages, such as:

The sender can fund any arbitrary redeem script without knowing what the spending conditions attached to the script are. This is an appropriate result because the sender of the transaction does not care how sent funds will be spent in the future. This is an issue for the recipient, who does care about conditions for further spending. The reduced transaction fee for the sender of the funds. Transaction fees are directly proportional to the size of a transaction, and a cryptographic hash of a fixed length allows the sender to send funds to any arbitrary redeem script without worrying about paying higher fees. It is the recipient’s responsibility to determine how large their spending transaction will be and how much it will cost, as they have to include the redeem script in order to spend funds. In other words, the burden of constructing the script and bearing the transaction fee of a long script is shifted to the recipient.



A common implementation of the P2SH function is the multi-signature address script. This script requires that a transaction possess more than one digital signature in order to prove ownership, and by extension spend funds. With P2SH transactions, the locking script is replaced with a redeem script hash. This hash derives from a redeem script, which functions similarly to the PubKey Script in that it too also contains conditions that must be satisfied before the output can be spent. When a transaction attempting to spend the UTXO is later initiated, the input must contain the PubKey Script (that contains the redeem script hash) and the unlocking script. In P2SH transactions, the script that houses the conditions for spending the output, which is the redeem script, is not presented in the locking script. Instead, only the hash (the redeem script hash) is included in the locking script, the redeem script itself is presented as part of the unlocking script when the output is spent. This has the effect of, as Andresen noted in BIP 16, of moving the responsibility for supplying the conditions to redeem a transaction from the sender of the funds to the redeemer.



Benefits of pay-to-script-hash:

The pay-to-script-hash feature offers the following benefits compared to the direct use of complex scripts in locking outputs:
- Complex scripts are replaced by shorter fingerprints in the transaction output, making the transaction smaller.
- Scripts can be coded as an address, so the sender and the sender’s wallet don’t need complex engineering to implement P2SH.
- P2SH shifts the burden of constructing the script to the recipient, not the sender.
- P2SH shifts the burden in data storage for the long script from the output (which is in the UTXO set and therefore affect memory) to the input (only stored on the blockchain).
- P2SH shifts the burden in data storage for the long script from the present time (payment) to a future time (when it is spent).
- P2SH shifts the transaction fee cost of a long script from the sender to the recipient, who has to include the long redeem script to spend it.
- P2WSH similar to P2SH but the hash of the script is different and the redeemscript itself goes in witness.
- P2SH-P2WPKH nested SegWit (workarounds) where it is similar to P2WPKH but the whole thing is put inside of a redeem script and hashed.
- P2SH-P2WSH same as previous one but for P2WSH.

Multi-Signature - (P2MS) scripts set a condition where N public keys are recorded in the script and at least M of those must provide signatures to release the encumbrance. This is also known as an M-of-N scheme, where N is the total number of keys and M is the threshold of signatures required for validation. For example, a 2-of-3 multi-signature is one where three public keys are listed as potential signers and at least two of those must be used to create signatures for a valid transaction to spend the funds.



At this time, standard multi-signature scripts are limited to at most 15 listed public keys, meaning you can do anything from a 1-of-1 to a 15-of-15 multi-signature or any combination within that range. The limitation to 15 listed keys might be lifted by the time this book is published, so check the isStandard() function to see what is currently accepted by the network.



Pay-to-Witness-Public-Key-Hash - (P2WPKH) has the same semantics as P2PKH, except that the signature is not placed at the same location as before. Segregated Witness (SegWit) moves the proof of ownership from the scriptSig part of the transaction to a new part called the witness of the input. Before SegWit the transaction signature was used in the calculation of the transaction id. The signature contains the same information as a P2PKH spend but is located in the witness instead of the scriptSig. The scriptPubKey is modified from.


A native P2WPKH address has prefix bc1q for Bitcoin mainnet. It uses the same public key format as P2PKH, with a very important exception: the public key used in P2WPKH MUST be compressed, i.e. 33 bytes in size, and starting with a 0x02 or 0x03. The P2WPKH scriptPubKey is always 22 bytes. It starts with an OP_0, followed by a canonical push of the keyhash (i.e. 0x0014{20-byte keyhash}).



P2WPKH address should be used when only 1 public key is used to receive payment (like a standard P2PKH address). Because the SegWit signature generating algorithm (described in BIP143) covers the value of the input being spent, a transaction spending a SegWit utxo can be signed securely by an air-gapped light-weight wallet or by a hardware wallet. P2WPKH addresses are Bech32-encoded according to BIP143: they start with bc1q.. for Bitcoin mainnet and are somewhat longer than traditional P2PKH addresses.

NULL DATA - (OP RETURN) is a script opcode which can be used to write arbitrary data on the blockchain and also to mark a transaction output as invalid. Since any outputs with OP_RETURN are provably unspendable, OP_RETURN outputs can be used to burn bitcoins. In version 0.9 of the Bitcoin Core client, a compromise was reached with the introduction of the OP_RETURN operator.



OP_RETURN allows developers to add 40 bytes of nonpayment data to a transaction output. However, unlike the use of “fake” UTXO, the OP_RETURN operator creates an explicitly provably unspendable output, which does not need to be stored in the UTXO set. OP_RETURN outputs are recorded on the blockchain, so they consume disk space and contribute to the increase in the blockchain’s size, but they are not stored in the UTXO set and therefore do not bloat the UTXO memory pool and burden full nodes with the cost of more expensive RAM. Keep in mind that there is no “unlocking script” that corresponds to OP_RETURN that could possibly be used to “spend” an OP_RETURN output.



The whole point of OP_RETURN is that you can’t spend the money locked in that output, and therefore it does not need to be held in the UTXO set as potentially spendable—OP_RETURN is provably un-spendable. OP_RETURN is usually an output with a zero bitcoin amount because any bitcoin assigned to such an output is effectively lost forever. If an OP_RETURN is encountered by the script validation software, it results immediately in halting the execution of the validation script and marking the transaction as invalid. Thus, if you accidentally reference an OP_RETURN output as an input in a transaction, that transaction is invalid. A standard transaction (one that conforms to the isStandard() checks) can have only one OP_RETURN output. However, a single OP_RETURN output can be combined in a transaction with outputs of any other type. Stealth addresses offer another example of OP_RETURN in action. This scheme enables payments to be received without publicly revealing the receiver’s public key or address. Data needed to make this system work are encoded within a call to OP_RETURN. In essence, Bitcoin does double duty as a secure messaging protocol.



You can use NULL DATA for data storage, because the standard script allows for a data push at the end.
So if you want to add some arbitrary data to a transaction; include an extra (empty) output, and place a NULL DATA locking script on it:



Non Standart - to include this type of transaction to the Bitcoin Blockchain, an agreement has to be reached with a miner: the non-standard transaction will be then included in the blockchain when the miner resolves the block. Depends on the hash rate from the miner it can be quite a while taking into consideration very high actual difficulty which is rising constantly from the start of Bitcoin. Of course, miner will take a proper fee for the non-standard transaction.

Bitcoin Transaction Types:

---

https://learnmeabitcoin.com/glossary/p2pk
https://learnmeabitcoin.com/glossary/p2ms
https://learnmeabitcoin.com/glossary/p2sh
https://learnmeabitcoin.com/glossary/nulldata
https://learnmeabitcoin.com/glossary/p2pkh
https://www.mycryptopedia.com/p2sh-pay-to-script-hash-explained/
https://bitzuma.com/posts/op-return-and-the-future-of-bitcoin/
https://www.cryptocompare.com/wallets/guides/bitcoin-transactions-pay-to-address-pay-to-public-key-hash/
https://www.cryptocompare.com/coins/guides/bitcoin-transactions-pay-to-script-hash/
https://www.cryptocompare.com/coins/guides/what-happens-to-a-bitcoin-transaction/
https://www.cryptocompare.com/coins/guides/how-does-a-bitcoin-transaction-work/
https://www.cryptocompare.com/coins/guides/what-are-the-bitcoin-transaction-types/
https://bitcoin.stackexchange.com/questions/64733/what-is-p2pk-p2pkh-p2sh-p2wpkh-eli5
https://bitcoin.stackexchange.com/questions/72194/why-dont-p2pk-scripts-have-their-own-address
http://bitcoinscri.pt/pages/segwit_native_p2wpkh_address
https://programmingblockchain.gitbook.io/programmingblockchain/other_types_of_ownership/p2wpkh_pay_to_witness_public_key_hash
https://en.bitcoin.it/wiki/Multisignature
https://bitcoin.org/en/glossary/null-data-transaction

I am very happy to announce that INV token is listed on the Ibitt exchange which of course belongs to Investa project. The first listed pair is USD-INV which is life and can be traded right now.

As for now, there is no volume and no buy orders, so no interested investors in buying INV token. I have to say that I thought it would happen and we have discussed this here in this thread and in the Telegram main Investa group.

The only way to attract investors to buy the INV token is a real use case which leads to adoption and real market value with demand for the token. Until the INV token will be not integrated into Investa products, like exchanges (fees, listings,etc.). ATM's, and all others from the lists.

Investa is not the only project which needs real use case for their token, to even dream about the adoption and demand, which will finally turn into buying pressure and growing volumes in INV trading pairs on Ibitt exchange.

The next step is an implementation of INV token into Investa product. If not, there will be no real use for the token and like any other projects, INV token will have no adoption which leads to no investors and slowly to 0$ price for the INV token. I have seen it already so many times that I am just 100% sure it will happen without real use cases for the INV token.

As for now, Investa team fulfilled almost all promises from the ICO. Of course, there are a couple left or are not fully developed yet, but the progress is really good and I believe that the implementation of INV token to Investa products will start right away.

It would be great to hear some answers from the team here in Bitcointalk thread, but as we all know they were not active here for a long time. I will try to ask these questions in the Telegram group and provide answers from the team here for all interested forum members who are invested, participated in bounty or simply follow this project.

Czyli wychodzi na to, że ci co zyskali na tym skoku ceny, to w jakiś sposób zostały im te wygrane cofnięte lub zatrzymane, a ci którzy stracili i tak musieli zapłacić swoje długi, czy tak?

Czyli jedynym kto wygrał były giełdy ale czy to prawda? Bo aż się wierzyć nie chce.

Zrozumiał bym taką sytuację, kiedy wszystko zostało cofnięte do stanu sprzed skoku ceny i ci co zyskali odeszli z kwitkiem ale ci co stracili, nie muszą nic oddawać i tym samym, kilku pechowców uratowano przed skokiem na główkę z biurowca siedziby giełdy  .

This is so sad that almost all discussions, especially about all new altcoins projects moved to Telegram. Bitcointalk was for me always the first place to go if I wanted to learn something about the project or to check the latest developments, actual progress, roadmap, insider news. Today I see almost no discussions in ANN threads and I am not talking about shitcoins only projects like EThLend for example. All I see are multiple questions from new accounts which tells me that the project uses bumping service to bring attention to the thread and project but such behavior brings only more suspicious members. It's a shame that Bitcointalk is losing the battle for discussions with other apps.

I agree with you that ignoring specific boards is just too extreme, taking into consideration that you ignore all additional child boards at the same time.

To be honest I never ignored an entire section and don't understand the reasons behind such a decision, especially now when the amounts of spam on the forum are significantly smaller.